Client to Handle Conversation, Presence and Heartbeats

[Charles Hudak]

The sending of the messages by the server to the client is the heartbeat.
Not sure why you think you'd need a separate heartbeat (channel).

On Mon, Sep 12, 2011 at 11:40 AM, Replicator <webakaunt at gmail.com> wrote:

> We need to have a client that is consuming messages from from the server (
> that we don't control ), and occasionally send messages to the server. For
> example:
>
>     1. client sends "I am up" message to the server
>     2. server sends "I know that you are up. Starting to send you stuff"
> message back to the client
>     3. server sends massive number of messages to the client
>     4. meanwhile client and server send each other heartbeats ( on the same
> port ) every second.
>
> Which messaging pattern can we use for this client? Or is it just as simple
> as having a client with registered upstream and downstream handlers that
> handle heartbeats, presence, etc.. messages?
>
> Thank you!
>
> --
> View this message in context:
> http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Client-to-Handle-Conversation-Presence-and-Heartbeats-tp6784800p6784800.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/20110912/269e94e5/attachment.html