[
https://jira.jboss.org/jira/browse/JBMESSAGING-544?page=com.atlassian.jir...
]
Tim Fox closed JBMESSAGING-544.
-------------------------------
Resolution: Done
Replace client-server transport with NIO based transport
--------------------------------------------------------
Key: JBMESSAGING-544
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-544
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Jeff Mesnil
Priority: Critical
Fix For: 2.0.0 Beta
For throughput and scalability we need to use a NIO model to provide connections between
jms clients and server.
Unfortunately the JBoss remoting model does not currently allows this.
We can either drive JBoss Remoting to support this model (may take some time)
Or write out own connection functionality - this could be fairly straightforward if we
use tools such as Apache MINA.
This would also solve the problem of providing a functional and performant multiplex
transport.
Essentially we need a bidirectional channel between jms client and server. On either end
bytes can be read or witten in a non blocking fashion.
On top of that we can introduce simple framing in order to provide multiplex
functionality.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira