Netty client

[Marc-André Laverdière]

No problem for #2. You just have to put a handler that will keep on
receiving the updates. When you get the update, you'll have to either
call your business logic, or send the data to a queue that will be
consumed by your business logic, or something along those lines. That
part is up to you.

And yes, Netty is perfect for what you are trying to do. You are
trying to do event-driven communication, and that's exactly what Netty
gives you.

Marc-André LAVERDIÈRE
"Perseverance must finish its work so that you may be mature and
complete, not lacking anything." -James 1:4
mlaverd.theunixplace.com/blog

 /"\
 \ /    ASCII Ribbon Campaign
  X      against HTML e-mail
 / \



2010/6/18 Murali Mohan Rath <mmrath at gmail.com>:
>
> Thank you Mate!
> I think implementing the decoders and encoders will not be difficult.
>
> The exact scenario is as follows:
>
> 1. Client sends a request to server and depending on server response client
> might send another request.
>
> 2. After the client's first request server will keep sending updates with
> out any client request and with no particular interval.
>
> I am not sure if 2 can be handled by netty (or asynchronously).
>
> If it is possible, can you please throw some light on it?
>
> Will netty provide any extra advantages than plain io/nio?
>
>
> PS: I am very new to socket programming.
>
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Netty-client-tp5193745p5194145.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
>