[CONF] Apache Qpid > Port server to new interface

[confluence]

Port server to new interface Page edited by Aidan Skinner Transport layer selection in o.a.q.server.Main Seperation of AMQP processing from networking QpidByteBuffer Change job processing Configuration to select a transport Transport layer selection in o.a.q.server.Main Main needs to be modified to remove the MINA specific option (NIO, MultiIO, executor pool etc) processing from there. Both bind methods should be moved to a networking class, along with parts of startup() and several of the private inner classes. Seperation of AMQP processing from networking AMQMinaProtocolSession needs to changed to decouple the AMQP semantics from the underlying networking. In particular, the threading model and idle timer related code should be removed. As a result, it should also be renamed. This will implement the ProtocolDriver interface. AMQPFastProtocolHandler and AMQPProtocolProvider should have their AMQP related functionality moved to to the AMQMinaProtocolSession replacement and their networking related functionality moved to the new networking layer. QpidByteBuffer At a number of points in the code we rely on behaviour particular to MINA ByteBuffers, in particular the auto-expanding functionality. To avoid having to rewrite those parts at this stage we should import the MINA ByteBuffer class as QpidByteBuffer and continue to use it as is. Change job processing Currently a number of unprocessed frames can be stored up in the Event/Job interface. This should be removed so that only one unprocessed frame at a time is allowed to exist. Configuration to select a transport Configuration needs to be added to support selecting one transport layer over another Change Notification Preferences View Online | View Change | Add Comment --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:commits-subscr...@qpid.apache.org