New Feature Request - Connection caching

[Simon Trudeau]

I have been an intensive Mina 2.x user for the past year and have always
liked the relatively simple use of the API over other NIO frameworks.
Unfortunately, what's always been a pain on the client side is the
connection management. There was no easy mechanisms for connection pooling.

My application needed to create 1000+ concurrent tcp client connection to
cellular devices. The connections couldn't be permanent, those devices could
only accept one connection at a time. Connecting again to a device would
cause the previous connection to get dropped.

What's really clumsy about the client API is this idea of connect - send,
when all we want to do is send and connect only if there are no opened
connections in the pool (establishing a connection takes a long time).
What's hard is to keep track in which state is the connection attempt
(attempting to connect, connected by attempting to disconnect, connected,
etc...). Also, what's complicated about developping your own connection pool
is the error management, you always have to check if the connection is still
valid, check that the connection future is not taking too long, etc...

It would really be appreciated if NETTY could provide developpers with
connection pooling capabilities.

I hope to see it in a future NETTY release. :.)


Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20081121/fcc1723b/attachment.html