So quiet here, wonder if any practical question can be asked here..
Link Mauve
catchycloud, you won’t know until you ask.
catchycloud
Just already ask in ejabberd muc, since my question related to ejabberd as broker.
Just about implementation
Link Mauve
Perfect then. :)
catchycloud
Just curious, wether we still something between mqtt - xmpp✎
catchycloud
Just curious, wether we still something between mqtt - xmpp data transport / communication ✏
Link Mauve
Both Ejabberd and Prosody support both protocols for c2s.
catchycloud
Just curious, wether we still need something between mqtt - xmpp data transport / communication ✏
Link Mauve
Perhaps other XMPP servers too.
Link Mauve
I have never tried MQTT though, I don’t even know what it looks like.
catchycloud
Just kind of udp , while xmpp looks more on tcp/ip
Link Mauve
It depends on how you use it, on XMPP you have three basic blocks (called stanzas), iq which is more like TCP (you get a reply always), message which is more like UDP (you send it to some other entity and perhaps will receive a reply if they feel like it, or perhaps an error at some point), and presence which is broadcasted with some rules.
catchycloud
Humm.. OK maybe I should read more detail. Already found two research papers related to this
Link Mauve
You can also read RFC 6120 which defines them.
debaclehas joined
Tobihas left
Tobihas joined
Tobihas left
Tobihas joined
catchycloud
This https://xmpp.org/rfcs/rfc6120.html ..
Soo many details to dig up ..
Tobihas left
Link Mauve
Section 8.2 is what you were asking about.
Tobihas joined
catchycloud
Uh yeah .. basic semantic.. right. Thanks pointed it
Tobihas left
Tobihas joined
Tobihas left
Tobihas joined
Tobihas left
Tobihas joined
Tobihas left
Tobihas joined
Tobihas left
Tobihas joined
Tobihas left
Tobihas joined
Link Mauve
Feel free to always ask around for guidance around reading stuff, if you feel like a spec or whatever is too impressive.
Link Mauve
A good place for discussing whatever you’ll be writing would be xmpp:jdev@muc.xmpp.org?join, a good place for discussing protocols would be xmpp:xsf@muc.xmpp.org?join
Link Mauve
And I’m out fetching breakfast, see you. \o_
Tobihas left
Tobihas joined
catchycloud
I hope I can manage more..
Jeroen.Naeffhas joined
MattJ
One thing to note about XMPP<->MQTT, I believe that while ejabberd supports both protocols, it doesn't actually bridge them. Prosody presents MQTT as an interface to XMPP's pubsub (XEP-0060) nodes
kapadhas joined
debaclehas left
kapad
» [10:13:29] <Link Mauve> It depends on how you use it, on XMPP you have three basic blocks (called stanzas), iq which is more like TCP (you get a reply always), message which is more like UDP (you send it to some other entity and perhaps will receive a reply if they feel like it, or perhaps an error at some point), and presence which is broadcasted with some rules.
👍 nice description ! The most you own a subject, the less words need to describe it ...