[jdev] Discovering the Federation.

Peter Saint-Andre stpeter at jabber.org
Wed Aug 30 14:57:05 CDT 2006

Sander Devrieze wrote:
> Op dinsdag 29 augustus 2006 22:59, schreef Cedric Hyppolite:
> <snip>
>> To solve the bootstrapping problem, the client would include an
>> initial list of stable, well-connected xmpp server which would be
>> used as a seed to discover the full network, then select which server
>> to register to. The advantage of this is to have an xmpp solution to
>> use on all the steps from 'I don't know jabber' to 'I have an account
>> and I chat with my friends'. In the same way as user directories are
>> handled by jabber instead of relying on web pages of user account
>> info, server directory could be handled by jabber.
> Try the account wizard of Coccinella ( http://hem.fyristorg.com/matben/ ; it 
> uses the XML file from jabber.org (though Peter should update that file).

Soon, very soon.

>> You can then imagine features in the client like selecting the server
>> based on values from the 'server statistics' namespace including
>> number of accounts, uptime, ping time, the availability of off-line
>> messaging, secure login...
> 1) Just add some additional fields to the XML file (uptime, services, number 
> of total/online users).
> 2) Automate the gathering of the information for this file with a bot (this is 
> what you want in every client, which would be IMO duplicative work).
> 3) Distribute the XML file (and its updates) with SourceForge.net (or 
> something similar) to make it distributed (SF.net has many download servers). 
> Client projects can also opt to serve that file on their server(s) for their 
> own client.

Good idea. We'll mirror the file once we get the new xmpp.net up and


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/20060830/b9de51d6/attachment-0002.bin>

More information about the JDev mailing list