[JDEV] JavaJabber Server Docs

David Waite dwaite at jabber.com
Mon Jul 9 15:05:43 CDT 2001

I would actually agree here. Nothing like a radically different 
implementation to point out things which are implementation-specific 
which were taken for granted. One of the fears I had was that the 
'newer' server developer would hit a lot of problems trying to implement 
something like 'presence' based on existing docs, and implementation 
just based on docs would create something which a lot of clients which 
have hacked against the implementation would not agree with. It would be 
a really bad if trying to do a different implementation caused them to 
get flak for implementing things in an incompatible way.

Luckily, I believe that Jabelin is considering starting a new server 
implementation and architecture themselves, meaning that it won't 
necessarily be 'us vs. them' when it comes to something that is 
implemented differently due to lack of specs. I really hope that people 
doing the actual implementation work are disciplined enough to document 
things they misunderstand :-)

-David Waite

Iain Shigeoka wrote:

>--- Jay Lorenzo <jlorenzo at uswest.net> wrote:
>>One thing I'd like to throw out here is the possibility of using a
>>design with the Jabelin folks. I think we may be best served by
>>participating in the design process with the Jabelin folks, which I
>>is just starting this process. We may want to consider having a 'subsig'
>>under Jabelin, using an 'org.jabber' namespace.
>I actually think it would better serve the Jabber 
>community if the two servers were developed 
>independently.  One of the more interesting things 
>I'd be looking for is what is implementaton specific 
>and what is standard Jabber.  This has been 
>exceedingly difficult to determine with just jabberd. 
>Something very different in implmentation could be 
>extremely useful...
>Do You Yahoo!?
>Get personalized email addresses from Yahoo! Mail
>jdev mailing list
>jdev at jabber.org

More information about the JDev mailing list