XSF Discussion - 2013-01-04

I see in my firebug window some very interesting websocket output

<stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='9b439c94-c8b7-4344-9b30-58dd3c46b6b2' from='localhost' version='1.0' xml:lang='en'>

<stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>SCRAM-SHA-1</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms></stream:features>

so mod_xmpp is now cutting the server stream into stanzas *and* removing <starttls/> from stream features

i think its damned close to first release time!

:)

afaik this is the first full implementation of xmpp over websockets

there's some rough edges in the last draft

arcriley: there are, please provide feedback to the xmpp@ietf.org list

arcriley: I thought that there was an implementation in ejabberd

is there?

the draft co-author worked on ejabberd at the time

and I know one person at the XMPP Summit last year had an implementation

ah cool

how did they hook into the webserver?

not sure

I didn't hear about the details

websockets support in webservers isnt exactly... yea

:)

thats why I wrote this, its the cleanest way to implement it without a bunch of hacks or http proxy stuff

apache doesn't proxy websockets correctly either

theres a module to implement websockets, but it seems to have an unstable api and you need to add an extra module on top of it to implement the protocol

arcriley we are using haproxy to proxy websockets - v1.5 is handling it very nicely for us

so at the last summit, there was discussion on integrating MAM with result sets

particularly on requesting pages in reversed order

so I've written up a potential addition to XEP-0059 to make that work: https://gist.github.com/4458101

Lance: excellent -- let's ping Matthew about that while we're at it (but you probably already have done so)

not yet, I don't think he's online

haven't seen him

but he is a man of many JIDs :)

indeed :)