Client to Handle Conversation, Presence and Heartbeats

[Replicator]

@Johnny,

    Right. If "performance permits", I would prefer to decouple different
protocol actions as different handlers => small handler is simpler, easier
to test, does only one thing as described in the protocol.

    If I go with that approach, is there a way to "route" different actions
to their corresponding handlers without hopping through the all handlers of
up/down stream sequentially?

Thank you!


On Tue, Sep 13, 2011 at 2:42 PM, Johnny Luong-2 [via Netty Forums and
Mailing Lists] <ml-node+s685743n6788785h34 at n2.nabble.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
> If the application logic is simple enough, one handler generally
> suffices; if not, you would probably need to make architecture decisions
> as to what warrants its own separate entity in the chain of
> responsibility (e.g: do I want this handler to handle this particular
> message).  This could mean using the Netty pipeline in the form of
> multiple handlers or having your single handler delegate the operation
> to your own internal processing flow.
> _______________________________________________
> netty-users mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=6788785&i=1>
> https://lists.jboss.org/mailman/listinfo/netty-users
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Client-to-Handle-Conversation-Presence-and-Heartbeats-tp6784800p6788785.html
>  To unsubscribe from Client to Handle Conversation, Presence and
> Heartbeats, click here<http://netty-forums-and-mailing-lists.685743.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=6784800&code=d2ViYWthdW50QGdtYWlsLmNvbXw2Nzg0ODAwfC0xODA0ODQ0MTcz>.
>
>


--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Client-to-Handle-Conversation-Presence-and-Heartbeats-tp6784800p6793278.html
Sent from the Netty User Group mailing list archive at Nabble.com.