Service registration for services (Was Re: [jdev] auto-updating server list)

[Trejkaz]

On Tuesday 14 March 2006 04:13, Peter Saint-Andre wrote:
> Trejkaz wrote:
> > On Monday 13 March 2006 00:13, Jesus Cea wrote:
> >> I agree :).
> >>
> >> I've thinking for ages about a central service registration for
> >> services. That is, that services available via XMPP can self-register in
> >> a "well known" service. And that service could provide search features
> >> for mere humans to locate available services.
> >>
> >> Let say, you are looking for a XMPP horoscope or translator bot...
> >
> > Or better yet, let's say you want to find a Jabber user but you don't
> > know what server they're on.  Hit this central service, it searches every
> > service it knows about until it finds the user. :-)
>
> Why not just let Google and other search engines spider the Internet for
> xmpp: addresses so we don't have to run such a service? Now, if someone
> wants to run a service like that it's great, but I'm not sure it needs
> to be centralized.

That's basically the same as what I was just suggesting, but indexing up-front 
somehow instead of performing the search on every server (your example 
suggests Google as the centralised service, but it's still centralised as far 
as I'm concerned.)

Of course, it will probably be a while until Google start using their XMPP 
service to go out and spider XMPP servers to find users.  And also XMPP 
servers currently have no way to list all their users anyway.  Well... unless 
you gave Google permission to view all the users via service discovery.  Then 
you could do some really interesting things.

TX

-- 
             Email: trejkaz at trypticon.org
         Jabber ID: trejkaz at trypticon.org
          Web site: http://trypticon.org/
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20060314/ae4aec84/attachment-0002.pgp>