IoT SIG - 2021-10-13

  1. SouL has left

  2. SouL has joined

  3. me9 has joined

  4. Tobi has joined

  5. me9 has left

  6. Syndace has left

  7. Syndace has joined

  8. Jeroen has joined

  9. Jeroen has left

  10. debacle has joined

  11. debacle

    MattJ So far, I don't even *want* to use MQTT :-) However, somebody asked "Can I use your XMPP PubSub based data thingy with MQTT, please?" and I try to get them used to XMPP first. Still, it is good, if I know beforehand, if there is any solution in case they remain stubborn.

  12. debacle

    But thanks for your offer - let's hope there is no need to actually try!

  13. Jeroen has joined

  14. Jeroen has left

  15. Jeroen has joined

  16. Jeroen has left

  17. Jeroen has joined

  18. debacle

    Just FYI: While Ejabberd does support MQTT, it is completely separated from the XMPP world. Bridging or mixing the two protocols is not possible.

  19. MattJ

    Huh, surprising

  20. debacle

    MattJ Yes, because that would make it interesting to use it for MQTT. If I need pure MQTT, I probably use a pure MQTT server. But maybe bridging is planned for the future, who knows.

  21. Jeroen has left

  22. Jeroen has joined

  23. Jeroen has left

  24. Jeroen has joined

  25. Jeroen has left

  26. Jeroen has joined

  27. Jeroen has left

  28. Jeroen has joined

  29. Jeroen has left

  30. Jeroen has joined

  31. Jeroen has left

  32. Jeroen has joined

  33. Jeroen has left

  34. Jeroen has joined

  35. Jeroen has left

  36. flow

    crazy that the MQTT stuff is in ejabberd then

  37. flow

    might as well run another stand alone MQTT server

  38. flow

    looks like prosody has the better feature set in this regard

  39. flow

    not that I aim to improve the ejabberd situation by starting some competition in this regard with this comment ;)

  40. Jeroen has joined

  41. Jeroen has left

  42. Jeroen has joined

  43. Jeroen has left

  44. Jeroen has joined

  45. MattJ


  46. MattJ

    I don't know how I feel now about the conversation I had when their blog post announced this ability

  47. MattJ

  48. MattJ

    The conversation focused on the fact that they didn't do it first, but now it seems they didn't do it at all :P

  49. MattJ

    I'm sure there is value in a massively scalable MQTT server written in Erlang, but without bridging between the two I don't know what the advantage is or why you'd call it a "dual-protocol" (to me that strongly implies two protocols to access the same data)

  50. MattJ

    *what the advantage is to building it into ejabberd

  51. MattJ

    I assume there is some code re-use

  52. me9 has joined

  53. Jeroen has left

  54. debacle has left

  55. me9 has left

  56. Jeroen has joined

  57. Jeroen has left

  58. Jeroen has joined

  59. Jeroen has left

  60. Jeroen has joined

  61. Jeroen has left

  62. Jeroen has joined

  63. me9 has joined

  64. me9 has left

  65. me9 has joined

  66. me9 has left

  67. Tobi has left

  68. debacle has joined

  69. debacle has left