Issue 48 in soashable: Explore Jive Connection Manager for Scalability
codesite...@google.com
http://code.google.com/p/soashable/issues/detail?id=48
Comment #7 by h.iverson:
No bites on Ignite Realtime forum. I've dug a little bit more (~30
minutes) and found
that the ConnectionManager singleton serves three purposes:
1. read and expose properties (server name, etc)
2. create and hold an instance of ServerSurrogate
3. start client listeners (xmpp, xmpp+ssl, httpbinding)
For our usage, we want to completely ignore #3. The main approaches
would be to
either factor that functionality elsewhere through
inheritance/delegation, or to
completely refactor the ConnectionManager. Or be completely ghetto and
use if
statements. I'd prefer the first option because it won't be much work
and it won't be
terribly inelegant and probably has the highest probability of being
accepted as a patch.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings