Implmenting http persistent connections

[Dai Jun]

Hi Milan,

I'am implementing a Bayeux codec, which a high-level protocol based on
other TCP/IP protocols, like HTTP (Persistent). IMO, if a client dose
not close a channel, it can always hold it and continuously receiving
data from server. It's not the responsibility of a thread pool. As I
know, the recommendation of section 8.1.4 of RFC 2616 is that "a
single user client SHOULD NOT maintain more than 2 connection with any
server". So, the number of connections in client should limit. I think
you can manage these connections in a non-complicated way, like
HashMap or List. BTW, I've post Bayeux codec here,
http://www.jboss.org/netty/community.html. I am very looking forward
to discuss it with any

Best regards,

Dai Jun or Danny Dai in English, http://guiwuu.googlepages.com
GTalk: guiwuu at gmail.com | QQ: 93409048 | MSN: guiwuu at hotmail.com |
Twitter: guiwuu



On Fri, May 15, 2009 at 1:51 AM, MilanB <milanbrahmbhatt at berkeley.edu> wrote:
>
> So, any ideas? Or should I be managing my own http connections on top of
> netty and implement the http persistent connections that way?
>
> Milan
> --
> View this message in context: http://n2.nabble.com/Implmenting-http-persistent-connections-tp2750721p2896803.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
>