mqtt-users team mailing list archive

[Nicholas Humfrey <njh@xxxxxxxxxx>]

On 12 Jun 2012, at 11:57, Toby Jaffey <toby@xxxxxxxxxxxx> wrote:

> Hi,
> 
> I'm interested to find out what MQTT to HTTP bridges/proxies exist and how they
> work.
> 
> Clearly, there's sometimes a need a need to provide access via web browsers to
> MQTT brokers. But, MQTT and HTTP are fundamentally different in their outlook.
> HTTP is a request response 1:1 while MQTT is asynchronous, event based pub sub.
> 
> Beyond browsers, providing MQTT broker access over HTTP allows for integration
> with existing services like Cosm's triggers, or ifttt.
> 
> The two bridges I have found handle the problem quite differently:
> Mosquitto's websocket bridge proxies raw MQTT over websockets - forcing the
> client to implement MQTT.
> 
> NJH's bridge (https://github.com/njh/mqtt-http-bridge) uses retained messages
> to map to HTTP's GET/PUT CRUD semantics. But, doesn't provide any mechanism for
> streaming messages.
> 

I am thinking about adding server sent event support to my bridge:

http://www.w3.org/TR/eventsource/

I think they align better with the web than sockets. But I think so might have to find somewhere else to host my bridge.


nick.