For what it's worth, we have a similar solution included in the Eurotech Everyware Cloud.
Device data can be equivalently published via MQTT or REST APIs.
Device data can be retrieved in real-time through MQTT subscriptions or AsyncREST/Comet subscriptions based on topic wild-card syntax defined by MQTT.
In addition, historical data can be queried only via REST APIs.
Here is a link to the related REST APIs documentation:
I apologize for the "unethical" advertising of a commercial product in an open source mailing list;
I am passing this along in case it may help the conversation with another example of MQTT<->HTTP/REST bridging.
-Marco
Absolutely, +1.
Would it make sense to invite the creator of QEST to present his work to the IWG?
I'm behind the current discussion trail that has formed behind this (all good stuff BTW !!!), but wanted to thank Andy for this link. Fantastic and clear notions behind this. To you point Andy, Scott and I are trying to keep this front and center and this is
good information.
Arlen
More on REST/HTTP and MQTT bridges - this rather lovely presentation:
and the associated new service:
http://qest.me
Per the conversation on the M2M IWG call today - here are a bunch of resources around HTTP and MQTT
_______________________________________________
m2m-iwg mailing list
m2m-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2m-iwg
_______________________________________________
m2m-iwg mailing list
m2m-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2m-iwg
_______________________________________________
m2m-iwg mailing list
m2m-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2m-iwg
|