[JDEV] The Important Things

[Al Sutton]

Why not add authentication and message relaying to the S2S protocol.

This would give four advantages;

1. Any user could log into any machine and the server would relay the
authentication request to the relevant machine to handle authentication.

2. The messages for that user would be relayed to the server they are
logged in to and then forwarded on to them.

3. Clusters or farms could be constructed to server a a single jabber
community and the load shared between them.

4. This would only involve a change to the S2S protol and servers
supporting it (of which there are few), and would leave the C2S protocol
unchanged and thus not require any client changes.

Comments?

Al. 

On Thu, 2002-01-10 at 15:50, Ashvil wrote:
> > I found that we could use some kind of a gateway -
> > people connect to one server ( for example jabbber.org ) autheticate -
> > get a token/session id - and then continue with a server
> > l1.l4.dddljfds.jabbber.org that are real jabber servers.
> <snip>
> 
> Any ideas that can help in scalability are welcome. If we can use a pool of
> cheap PCs to build a scalable jabber network, then even more valuable then
> having One big Server with Gigs of memory.
> 
> This will require some changes in the Jabber protocol. The MSN protocol does
> something like this, but takes this one step ahead by letting you connect to
> any server in the pool, which then refers you to the right server that can
> authenticate you. If you make logging in a two-step process, you can solve
> this problem but that would mean changing all the Jabber clients and also
> the S2S communication in the Jabber server.
> 
> Anyway, this is an area that the Jabber server developers are the best folks
> to comment on.
> 
> Regards,
> Ashvil
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev