Thanks, Some of these scalability concerns may stem from my unfamiliarity with the current sizing and scalability of the system. Perhaps a Dual PIII 1Ghz 2G Ram can support 100,000 concurrent clients already if traffic is low.
On the stateless UDP model, doesn't that also help reduce the keepalive traffic required to prevent the connections from idling out? (NAT cleans up connection)? Noticed some interesting dicussion on the JNG list, but I assume that stuff is way off in the future... - August ----- Original Message ----- From: "DJ Adams" <[EMAIL PROTECTED]> > > do a stateless version of the jabber transport in something like UDP which > > I've not looked at it in a while, but jer did some work under the "WCS" > umbrella that allowed a stateless connection, the conversational elements > of which were carried via XML-RPC. Perhaps there's mileage in this. > > There are a number of projects past and present whose purposes have been > to address areas of scalability; one current one, from the jabber.com stable, > is CCM (client connection manager). But I'll let someone else expand on > that :-) > > dj > > ----- End forwarded message ----- > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
