Hi all,

I'm interested in contributing to the Synapse project. As my initial step
I've implemented the Resequencer EAI pattern [0] for Synapse.

*Importance of a Resequencer*
As messages passing through Synapse they'll mediate through various paths.
So the order of the receiving messages may differ from sending order. For
some occasions this order matters. For those situations Resequencer is the
solution.

*Implementation*
My implementation of Resequencer is based on message processor concept.
This processor can be plugged in to any kind of message store already
exists. So processor goes through those messages and sends messages out to
another sequence. So such a system has the flexibility of plugging in to
various situations. Specifying the sequencer number of the message is
configurable.

*Further Details*
For the new implementation I had to change the implementation of
MessageProcessorFactory for giving ability to read parameters with
expressions. Then message processor reads the messages in a given store
time to time and send them to another sequence in an order.

So far I have almost completed my implementation of this according to the
details mentioned and I'm willing to hear your opinions on this.

*References*
[0] http://www.eaipatterns.com/Resequencer.html

Thank you!
-- 
Buddhima Wijeweera,
Undergraduate,
Department Of Computer Science and Engineering,
University Of Moratuwa,
Sri Lanka.

Reply via email to