- What would the CM be in charge of besides obviously managing the connections?
I think it would be helpfull to roughly itemize what each component would be in charge of and what sub-components would comprise each. I can see the CM needing at least an authentication manager connected to it.
Aside from making the tcp connection itself, depending on the authentication provider, authentication is probably more of an expensive operation than anything else. Taking care of that on the CM makes sense, but then each CM would need a handle on an authentication manager and it’'s respective configuration and policies.
I guess what I’'m getting at is what core components stay in ‘‘Core’’?
Do we need a new protocol and JEP for this? It really seems almost implementation specific as to how to distribute the load of concurrent connections. Would we create a JEP for XMPP clustering and failover next?
Instead of a CM protocol, what about RMI and core services plucked out of JNDI?
Code could generally stay the same, just getInstance()s could be re-implemented.
just my 3c,