I do agree we haven't pursued the pubsub for IoT yet I am doing it very
simple using MUC rooms today sending xep 323 message events with
type="groupchat" to a MUC room meaning that the MQTT topic is the MUC room
name/topic and there is one moderator who is "publishing" and anyone
joining the room either white listed or not blacklisted can start listening
and silently agreeing not to sending by it self.
/joachim
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin:
http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
2015-04-29 11:02 GMT+02:00 Cramer, E.R. (Eelco) <Eelco.Cramer(a)tno.nl>nl>:
For a project that I’m doing with several partners
I’m proposed to use
the XMPP IoT experimental extensions (including the not yet submitted
eventing extension). One requirement for the project is that the ‘Things’
should use as little data as possible and for this we wanted to optimise
the data the Things are sending to subscribers. Another requirements was
that we would like to be able to have fine grained control on which
subscribers would be allowed to subscribe and receive the data.
We want to accommodate multiple listeners to the same events, this is
quite pub/sub like, and discussed to use either MQTT or XMPP.
A few things I noticed during our discussion:
1. The partners did not see the eventing extension as pubsub but
rather as p2p because clients need to subscribe to all the different things
instead of to only a single topic.
2. There is currently no best practises in using pubsub or PEP for IoT.
3. Management of pubsub nodes (manage subscribers and publishers) is
cumbersome and not all functions (authorization schemes) are supported by
all XMPP servers.
4. I proposed an alternative pubsub like service, that I called
‘dealer’, which acts as a IoT concentrator towards the subscribers and that
would subscribe to all Things the clients would want to receive events from.
Currently the project is leaning towards MQTT, mostly because partners
like that concept of pubsub over the XMPP alternatives (verbosity of XMPP
is not considered an issue).
I would like to share this feedback as it might be useful in progressing
the IoT extensions further.
Cheers,
Eelco
This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message. TNO accepts no
liability for the content of this e-mail, for the manner in which you use
it and for damage of any kind resulting from the risks inherent to the
electronic transmission of messages.
_______________________________________________
IOT mailing list
IOT(a)xmpp.org
http://mail.jabber.org/mailman/listinfo/iot