State machine driven by messages

[Dmitry Voronov]

Hello Daniel!

I use multiple handlers, representing states.
Each handler got it's own timers, scheduling and cancelling on pipeline
events.

This scheme fulfills all my needs in stateful bgp conversations for example.
Hope this helps :)

-- 
Best Regafds,
Dmitry J. Voronov


On Tue, Jul 13, 2010 at 6:47 AM, Daniel Ferber <dffforum at gmail.com> wrote:

>
> Hi,
>
> I am thinking about a service that consists of a client-server
> conversation.
> I found netty the ideal solution to convert the socket stream to
> conversation message objects and back.
>
> Now I am wondering if there is another complementary framework that would
> help me managing the sate of each conversation (the is one conversation for
> each connection received by netty).
>
> I imagine a set o active conversations. A set of worker threads would watch
> the set of conversations. If there is a conversation with a pending message
> from the client, then a worker thread would take on the conversation and
> send a message back to the client. Conversation that remain idle for too
> long get killed.
>
> I would appreciate much any advices about the existence of such
> complementary framework, or if I shall implement this from scratch.
>
> Daniel Felix Ferber
>
> --
> View this message in context:
> http://netty-forums-and-mailing-lists.685743.n2.nabble.com/State-machine-driven-by-messages-tp5285744p5285744.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20100713/f0257d1d/attachment.html