Rule for multiplicity of channels to remote hosts.

[Will S.]

Hello,

What is best practice when I'd like to send *multiple concurrent* requests
to the same remote host, via the Channel? Is it safe for multiple threads to
share the same Channel object connected to the same remote host and perform
concurrent write(Object message)?

I am wondering if the better approach is to control this more on my side by
queuing requests accordingly, or potentially opening multiple channels (and
eventually reusing) to write multiple concurrent objects.

Hopefully this is clearly stated; please let me know otherwise. 

(I'm a Netty newbie; but I compliment Trustin and his team on the nice work
(and documentation!) they have assembled.)

Thanks!
Will
-- 
View this message in context: http://n2.nabble.com/Rule-for-multiplicity-of-channels-to-remote-hosts-tp4914969p4914969.html
Sent from the Netty User Group mailing list archive at Nabble.com.