[JDEV] ATTENTION JABBER SERVER DEVELOPERS

[Robert Norris]

> We are updating the software listings at jabber.org (and preparing for
> software listings at xmpp.org). Eventually we will update the client, 
> component, and library listings, but the first step is to update the 
> server listings. These listings will be much more complete than what is
> at <http://www.jabber.org/admin/serverlist.php> right now. In order to 
> update the listings, I need to gather detailed information about each
> server in the list. Therefore please send me a message off-list about
> which of the following you support:

I'll email you seperately about j2. Just a couple of queries about this
list:

> JEP-0004 (x:data interfaces to the server)

What does that mean? x:data doesn't mean anything without context (like
x:data bits in registration, ad-hoc commands, etc).

> JEP-0106 (jid escaping)

What does this mean for a server? It doesn't seem (from a quick reread
of the JEP) that servers actually have to do anything with an escaped
JID.

> storefile (data storage on the file system)
> storeldap (data storage in LDAP)
> storeberkeley (data storage in Berkeley DB)
> storepostgres (data storage in PostgreSQL)
> storemysql (data storage in MySql)
> storemssql (data storage in MS SQL Server)
> storeoracle (data storage in Oracle DB)
> storeactivedir (data storage in Active Directory)
> storeother (data storage in some other storage system)

Does an authentication source count as "data storage"? eg, j2 can auth
against users stored in LDAP, but no user data is actually stored in
LDAP.

> These are all boolean -- either you support them fully or you don't. If
> you have been tracking the XMPP specs but support some really recent
> version rather than the ones I published just the other day, we'll cut
> you some slack and call your support complete. (If you support the XMPP
> specs, we will list you at xmpp.org once that is up and running.)

> These seem like the most important features, but feel free to suggest 
> others. Perhaps items for the ability to connect or send messages via 
> SMS, WAP, Wireless Village, SIP/SIMPLE, etc.? (The current features for 
> "MS Exchange Integration" and "Netmeeting Integration" are not clear to 
> me and to others who've asked me about them, which is why I've removed 
> them from the list, but I can be convinced to add them back.)

They sound more like transport features. If they're bundled with the
server, then perhaps, but I can see a case where a server that comes
with, say, a SIMPLE transport looks more featureful than a server that
isn't bundled with one but can use a third-party version. This argument
could also be made for features like "message logging".

I'm just trying to skew it to make jabberd2 look the best, of course ;)

Nice stuff :)

Rob.

-- 
Robert Norris                                       GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx                Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://www.jabber.org/jdev/attachments/20031030/e0cb3fc0/attachment-0002.pgp>