[jdev] machine-readable server & transport list

[Norman Rasmussen]

On 8/10/07, Jonathan Chayce Dickinson <chayce.za at gmail.com> 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.

hear, hear.  I want a list of servers that I can search based on their
subnodes.  That way it would be easy to find a transport to do 'blah'.
 In fact while we're at it, you can add uptime or each node so that
it's easy to tell which transports are stable, and which are flaky.

-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/