Uploaded image for project: 'MINA'
  1. MINA
  2. DIRMINA-453

Multiple IoServices for one java.nio.Selector

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0-M1
    • 2.0.8
    • Core
    • None
    • All

    Description

      Please see the discussion:

      http://www.nabble.com/multiple-handlers-per-IoService-t4481513s16868.html#a12779214

      Based on discussions with Trustin, this is functionality that will be in the 2.0 release. It seems to be inefficient to create a new selector/thread for each IoService. This means that an application that is listening on 2 ports, would need two java.nio.Selectors, two Selector worker threads and each have a pool of workers.

      Not only does this create much duplication, but more threads will be created than may be necessary.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            elihusmails Mark Webb
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment