[jdev] Re: help needed to implement a P2P Chat Client

Peter Saint-Andre stpeter at jabber.org
Mon Aug 28 13:27:30 CDT 2006

Ravi wrote:
>> Why? How many simultaneous connections do you expect? Do you really know
>> that the existing client-server model won't work? It seems to work just
>> fine for lots of large deployments!
> The goal is to be able to scale to millions of logged in users. I did
> not find any existing scalability numbers for ejabberd, are there any
> load test numbers for ejabberd (or any other server)? Since it is
> reasonable to assume that P2P chat will substantially increase
> scalability and decrease bandwidth requirements. Hence the need.

Most organizations who need that kind of scalability write their own
implementations (e.g., Google Talk) or use one of the commercial XMPP
server products. But don't assume that p2p would solve all your problems.

>> No, Jingle is not trying to address this. Jingle does signalling over
>> the XMPP channel and media over RTP or whatever.
> Correct me if I am wrong, as I understand jingle will help establish a
> P2P connection. Once connection is established, I can deviate from the
> specs and use my own protocol for exchanging chat messages. Finally I
> can use jingle again to close the session.

Sure, you could do that. In fact it would just be a new Jingle content
type (Jingle is extensible, so what you're proposing doesn't really
deviate from the specs).


Peter Saint-Andre
Jabber Software Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20060828/594e45ef/attachment-0002.bin>

More information about the JDev mailing list