<mort___>
hannes: xmpp implementation finished (in the sense that the dissertation is now done and about to be handed in) — https://github.com/jeffa5/mirage-xmpp
<mort___>
i just signed off on demos for both of them
<mort___>
xmpp was using psi as the client to subscribe to presence, exchange messages etc
<mort___>
but there are lots of XEPs that are not implemented of course
<mort___>
0mq was using the python zeromq bindings as the client to create REQ/REP and PUB/SUB instances to exchange messages
<mort___>
XPUB/XSUB also implemented i think
<mort___>
but again, there are many extensions not implemented
<mort___>
i pointed both students heavily at the tls, arp and bgp implementations for inspiration how to structure their code
<mort___>
so hopefully at least somewhat usable...
pie__ has quit [Ping timeout: 255 seconds]
<Drup>
I was talking about xmpp, and practically usable = able to define a reasonably-featured bot for rooms, for instance
<dinosaure>
which is a good start :)
Haudegen has quit [Read error: Connection reset by peer]
<hannes>
mort___: yeah, for the xmpp (which I'm pretty interested in), I'd like to know what is there and what not? this spans over: TLS, server-to-server connections (with their weird callback crap), authentication (which methods / what is used as data store).
<hannes>
but then, I can likely also just read the code and get an idea about that (which I will do anyways eventually before using it)
<hannes>
i also have some further interest, to look at the xml parsing and see whether I can replace erm-xmpp that i use atm in my xmpp-client with that parser..
<mort___>
xmpp — i think the answer is none of those (tls, s2s connections, authentication) and the datastore is an in-memory Map