Dnia 2008-02-27, Śr o godzinie 04:48 +0100, Andrew Miehs pisze: > Would I need to create one connection to the jabber server for each > web user, or can > I use one connection per web server? I am a little worried about how > well thousands > of connections per server would scale.
Many jabber servers use a concept of client connection manager, that mediates connections between jabber clients and jabber server. These managers might be deployed on separate machines, handle thousands client connections and pipe the messages through one connection to the jabber server. You might consider implementing your web gateway to work as such connection manager utilising connection manager protocol. You wouldn't need to open client connections from your web server, log in and do the whole session establishing burden on the web server. Instead you just send session-start command to the server when you have new web frontend user logged in, and you're done. There is jadc2s that works with jabberd 1.x and jabberd 2.x has its own c2s component bundled. jabberd 2.x component protocol is a bit documented at http://jabberd2.xiaoka.com/wiki/ComponentProtocol (look at the SM<->C2S protocol). -- /\_./o__ Tomasz Sterna (/^/(_^^' http://www.xiaoka.com/ ._.(_.)_ im:[EMAIL PROTECTED]
