[jdev] Collaboration on BOSH servlet?
Peter Saint-Andre
stpeter at stpeter.im
Wed Jan 9 11:13:57 CST 2008
Alexey Nezhdanov wrote:
> On Wednesday 09 January 2008 08:08:05 Greg Wilkins wrote:
>> The BOSH spec looks pretty straight forward and very similar to what we
>> have for Bayeux/cometd I should be able to implement that in a week or so.
>> But will that be sufficient for XMPP clients and servers to use it or
>> will I need to write some XMPP adaption/integration stuff as well?
> Well, that depends on what you are calling 'XMPP integration'.
> Yes, I think you'll need somewhat light-to-medium integration. Before it was
> the single spec (http-bind), but later it was split in two to clearly divide
> transport stuff from protocol stuff. Still, as I understand - stream
> initiation/termination and may be stream errors passing also should be
> handled separately.
> Though, if you just implement what is required in XEP-0124 that should be just
> enough and there wouldn't be need for questions like 'do I need to implement
> xmpp integration stuff'.
Right. The core streaming stuff is in XEP-0124, which BTW we might take
to the IETF for standardization there. A while back, Ian Paterson split
out the XMPP-specific stuff from XEP-0124 and placed it in XEP-0206
("XMPP Over BOSH"). But implementing XEP-0124 should get you 90% of the
way there.
Feedback is welcome on the spec and any implementation challenges you
run into. I know there has been discussion on the standards at xmpp.org
list about some ambiguities in XEP-0124, and we may run through it at
some point to clarify those issues. So let us know!
Thanks for working on this -- it seems like we're seeing more BOSH
implementations, which will help us ensure interoperability over time.
Peter
--
Peter Saint-Andre
https://stpeter.im/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20080109/97f2e523/attachment-0002.bin>
More information about the JDev
mailing list