[Jwchat-devel] jwchat, protocols, and supported servers

[Hans L. <ha...@ve...>]

Hi,

I know this is probably a frequently asked question, but I can't find 
much documentation on this.  For those of us (I hope I'm not alone) that 
don't know the gritty details of the jabber protocol, there seems to be 
a number of different technologies & protocols at work.  I understand 
that the main issue with using jwchat with a jabber server is that the 
jabber protocol by nature is not HTTP/stateless- friendly.  So, as I 
understand it, hence WCS and HTTP Polling and now most recently HTTP 
binding.

My question, I guess, is what exactly is current CVS of jwChat 
requiring.  And what are my server options?

  * I know I can use Ejabberd, but this really isn't an option for us, 
since it's written in such an obscure language (I work with a security 
firm, so we need to be able to audit the server software).

  * I have tried [so far unsuccessfully] to get Punjab to work with 
jwChat + jabberd 1.4.x.  This *seems* like it should work, but I'm stuck 
now with some strange Python exceptions ("Data must be a string") in my 
twistd.log.

  * I understand there is a Java server / gateway also?  That's not 
ideal, but might be good as proof of concept.

  * I understand that support for HTTP binding (or is it polling) is 
also planned for Jabberd 2.1, but that doesn't seem to exist yet.

Ideally, I'd like to use jwChat with jabberd 1.4.x or jabberd 2.x.  Is 
there anyway to do this?  Does CVS jwChat still work with the WCS module 
or does jwChat absolutely require a server that supports these HTTP 
protocols?

Thanks in advance!

Hans