IoT SIG - 2023-03-10


  1. debacle has left

  2. Tobi has left

  3. Tobi has joined

  4. Tobi has left

  5. Tobi has joined

  6. Tobi has left

  7. catchycloud has joined

  8. Tobi has joined

  9. Tobi has left

  10. Tobi has joined

  11. Tobi has left

  12. Tobi has joined

  13. Tobi has left

  14. Tobi has joined

  15. Tobi has left

  16. Tobi has joined

  17. Tobi has left

  18. Tobi has joined

  19. Tobi has left

  20. Tobi has joined

  21. catchycloud

    So quiet here, wonder if any practical question can be asked here..

  22. Link Mauve

    catchycloud, you won’t know until you ask.

  23. catchycloud

    Just already ask in ejabberd muc, since my question related to ejabberd as broker. Just about implementation

  24. Link Mauve

    Perfect then. :)

  25. catchycloud

    Just curious, wether we still something between mqtt - xmpp

  26. catchycloud

    Just curious, wether we still something between mqtt - xmpp data transport / communication

  27. Link Mauve

    Both Ejabberd and Prosody support both protocols for c2s.

  28. catchycloud

    Just curious, wether we still need something between mqtt - xmpp data transport / communication

  29. Link Mauve

    Perhaps other XMPP servers too.

  30. Link Mauve

    I have never tried MQTT though, I don’t even know what it looks like.

  31. catchycloud

    Just kind of udp , while xmpp looks more on tcp/ip

  32. 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.

  33. catchycloud

    Humm.. OK maybe I should read more detail. Already found two research papers related to this

  34. Link Mauve

    You can also read RFC 6120 which defines them.

  35. debacle has joined

  36. Tobi has left

  37. Tobi has joined

  38. Tobi has left

  39. Tobi has joined

  40. catchycloud

    This https://xmpp.org/rfcs/rfc6120.html .. Soo many details to dig up ..

  41. Tobi has left

  42. Link Mauve

    Section 8.2 is what you were asking about.

  43. Tobi has joined

  44. catchycloud

    Uh yeah .. basic semantic.. right. Thanks pointed it

  45. Tobi has left

  46. Tobi has joined

  47. Tobi has left

  48. Tobi has joined

  49. Tobi has left

  50. Tobi has joined

  51. Tobi has left

  52. Tobi has joined

  53. Tobi has left

  54. Tobi has joined

  55. Tobi has left

  56. Tobi has joined

  57. Link Mauve

    Feel free to always ask around for guidance around reading stuff, if you feel like a spec or whatever is too impressive.

  58. 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

  59. Link Mauve

    And I’m out fetching breakfast, see you. \o_

  60. Tobi has left

  61. Tobi has joined

  62. catchycloud

    I hope I can manage more..

  63. Jeroen.Naeff has joined

  64. 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

  65. kapad has joined

  66. debacle has left

  67. 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 ...

  68. catchycloud has left

  69. catchycloud has joined

  70. kk has joined

  71. Jeroen.Naeff has left

  72. kk has left

  73. kapad has left

  74. debacle has joined

  75. kk has joined

  76. Vaulor has left

  77. Vaulor has joined

  78. debacle has left

  79. debacle has joined

  80. Tobi has left

  81. Tobi has joined

  82. Tobi has left

  83. Tobi has joined

  84. Vaulor has left

  85. Vaulor has joined

  86. Tobi has left

  87. Tobi has joined

  88. Tobi has left

  89. Tobi has joined

  90. Tobi has left

  91. Tobi has joined

  92. kk has left

  93. Vaulor has left

  94. Vaulor has joined

  95. catchycloud has left

  96. catchycloud has joined