RE: [JDEV] Re: Jabber registry

["Patrick McCuller" <patrick@kia.net>]

	The proposal is fine as it is, but this is exactly what LDAP is *for*.  You
don't need to invent or write anything, including a data store, LDAP
interfaces are well known, documented, and stable, and existing LDAP servers
could be tapped for user profile information. LDAP servers can be backed up,
replicated, and so on, all independantly of jabber. Additionally, LDAP
authentication will be integrated into Jabber servers (a mod_ldap,
undoubtably) eventually, probably sooner rather than later.

	With LDAP as the registry, users could search or update the registry using
standard tools, or a web interface. LDAP client libraries are relatively
easy to integrate with both clients and servers.

	There is also a good free LDAP server at http://www.openldap.org/ which I
can vouch for. The web hosting company I work for uses it exclusively, and I
do all of their LDAP-related development.

	Not to try to convince you or anything.  :)


Patrick



> -----Original Message-----
> From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of
> Jeremie
> Sent: Thursday, July 29, 1999 6:26 PM
> To: jdev@jabber.org
> Subject: [JDEV] Re: Jabber registry
>
>
> > Sure thing. I don't care how it is stored, so long as the information
> > is easily available to jabber clients so they can look it up when
> > sending messages. I saw the roster as being the single store for all
> > relevant info on users. Being a newvomer I may have overlooked this
> > part. Are there any docs on a profile store/registry? Any substantial
> > thoughts in the matter?
>
> Yes, I wrote up a quick proposal some time ago at:
> http://www.jabber.org/developers/archive/9904/msg00022.html
>
> It's partially implemented already, and I plan on having it ready to test
> by 0.7.  There have been a few changes/updates and there needs to be a
> good deal more documenting/explaining on it, which is all on it's way
> after I get caught up on other things.
>
> Jer
>
>