[CONF] Apache Qpid > Port server to new interface

[confluence]

Port server to new interface Page edited by Aidan Skinner Overview Refactoring MINA dependencies Transport layer selection in o.a.q.server.Main Separation of AMQP processing from networking Change job processing Configuration to select a transport Overview This component element is comprised of the following sub-tasks: Existing code needs to be refactored to remove dependence on MINA Existing code ported to use new common interface Configuration to select a transport QpidByteBuffer Change job processing These tasks are described in more detail below. Refactoring MINA dependencies Transport layer selection in o.a.q.server.Main Currently the broker's Main method contains setup code specific to MINA. Main needs to be modified to remove the MINA specific option (NIO, MultiIO, executor pool etc) processing from there. This should be replaced with creation of a Network Driver instance with configuration being picked up & applied in a standardised way. Both bind methods should be moved to a networking class, along with parts of startup() and several of the private inner classes. Separation of AMQP processing from networking Class Changes AMQMinaProtocolSession decouple the AMQP semantics from the underlying networking. In particular, the threading model and idle timer related code should be moved to the NetworkDriver implementation. As a result, it should also be renamed to AMQProtocolEngine, with _8_0 and _0_9 delegates for handling protocol specific functionality. This class will implement the ProtocolEngine interface and become the central point for processing AMQP frames. AMQPFastProtocolHandler AMQP related functionality combined in the ProtocolEngine and networking related functionality moved to the NetworkDriver implementation. AMQPProtocolProvider AMQP related functionality combined in the ProtocolEngine and networking related functionality moved to the NetworkDriver implementation. 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. Note that this functionality is not related to the network buffers, the QpidByteBuffers are the outputted data structure. The existing implementations will have their MINA or java.nio.ByteBuffers converted to QpidByteBuffers by the ProtocolEngine. AMQDecoder Should no longer extend CumulativeProtocolDecoder Event, Job Created by AMQProtocolEngine.recieved rather than AsynchPoolingFilter Change job processing Currently a number of unprocessed frames can be stored up in the Event/Job interface. This should be changed so that only a finite number are held in AMQProtocolEngine waiting to be processed. 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