[jdev] machine-readable server & transport list

[Peter Saint-Andre]

Jonathan Chayce Dickinson wrote:
> On Fri, 2007-08-10 at 12:00 -0600, Peter Saint-Andre wrote:
>> Jonathan Chayce Dickinson wrote:
>>> I think you have hit on another problem as well. How do we describe a
>>> Jabber Server? 
>> Why do we need to list every service that a server offers? What is the
>> use case? A user can register with services on other servers once on the
>> network, and those can be discovered with service discovery (XEP-0030).
> 
> Oops. However, worst case scenario:
> 
>       * 5 servers support smtp-jabber.
>       * 200 server almost identical (XEP Server 2007).
>       * 300 servers in total.
>       * User wants to get one of those smtp-jabber servers.
> 
> Can you see the users' dilemma? They would have to spend hours sifting
> through 300 servers to find one of 5 (a 1-2% chance on the first try!).
> Getting a computer to do a search through this O(n) scenario would be
> justifiable. Even if they register with any server, they still have to
> find another one.

I think you want more than a simple XML file -- you want a searchable
directory of XMPP servers, as if Google went out and spidered the XMPP
network to find information about XMPP addresses (could be servers,
could be components like chat room services or chat rooms, could be
users). That would be pretty cool. :)

/psa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7354 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20070810/bf877f8e/attachment-0002.bin>