[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-92) Integrate and enable multiplex transport

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-92?page=all ]

Tim Fox updated JBMESSAGING-92:
-------------------------------

    Fix Version/s:     (was: 1.2.0.Alpha1)
                   1.2.0.Beta1

> Integrate and enable multiplex transport
> ----------------------------------------
>
>                 Key: JBMESSAGING-92
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-92
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Remoting
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ron Sigal
>            Priority: Critical
>             Fix For: 1.2.0.Beta1
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> Replace "Connector per Consumer" solution with a Remoting UIL2-like transport
> The ConsumerInterceptor creates a new Connector instance per each Consumer, and associates maintains a reference to it as transitory metadata, so it can shut it down when the Consumer closes. 
> The Connector is necessary as a callback server for asynchronous notifications. The MessageCallbackHandler instance is registered to it. Maintaining an instance per Consumer is necessary to avoid port conflicts.
> This is a temporary solution until JBoss Remoting gets an UIL2-like transport.
> As long as we maintain a server socket per consumer, it won't be possbile to receive asynchronous notifications over firewalls.
> until multiplex performance is better it should not be the default tranport but should be available nevertheless

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira