> Hmm... As I'm typing this, I an idea came to me. Originally, I had dismissed > using a separate client class because it would be difficult to tie the > connection limits together. What just occurred to me (duh), is that the > connection manager is a separate object. The second client class wouldn't use > any request interceptors. Can you see any problems with sharing the same > instance of connection manager between two different client objects/classes?
AFAIK, that's a perfectly valid use. (Whether or not it's the intended use... I'm not sure. We definitely use it that way within LimeWire, though.) Sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
