[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [paho-dev] MQTT <-> REST+websocket mapping
|
Dave,
I agree - there shouldn't be a separate port for MQTT over WebSockets. Ordinarily, the browser will expect a WS / WSS connection to go over the port the page loading the JS was served from. Cross Origin (CORS) WebSockets are possible, too, but the expectation is that they would be using normal HTTP or HTTPS ports. WebSockets aren't much more than a tunnel for TCP through a HTTP endpoint...
What there is needed, though, is an IANA Websockets subprotocol registration. This allows one HTTP endpoint to serve different protocols to the same relative URL path. Why does this matter? Well, it means a lot of servers only need to have, say, /websockets-be-here set up. It also allows protocol negotiation, which is useful if you serve multiple versions of the same protocol, or allow STOMP and MQTT to co-exist. (Perhaps you're serving up a MQ, but some clients only use MQTT and other s STOMP).
Raph
Raphael Cohn
Chief Architect, stormmq
+44 7590 675 756
UK Office:
Hamblethorpe Farm, Crag Lane, Bradley BD20 9DB, North Yorkshire, United Kingdom
Telephone: +44 845 3712 567
Registered office:
16 Anchor Street, Chelmsford, Essex, CM2 0JY, United Kingdom
StormMQ Limited is Registered in England and Wales under Company Number 07175657
StormMQ.com
On 18 March 2013 10:51, Dave Locke
<locke@xxxxxxxxxx> wrote:
not sure that a separate port is needed
for MQTT over WebSockets. Why not piggy back on the standard MQTT
ports or the standard HTTP ports? One of the proposed benefits
of WebSockets is that it should make it easy to traverse firewalls and
proxies...
All the best
Dave
From:
Raphael Cohn <raphael.cohn@xxxxxxxxxxx>
Date:
17/03/2013 19:06
Yes, I mean a websocket subprotocol. Best to nab it -
I'd be happy as it being registered by Eclipse / Paho. The other alternative
is to have it registered by the about to be established OASIS TC, which
might gie it more weight in some eyes. (it's possibly moot). But the OASIS
TC isn't planning AFAIK to start doing any work on standardising a websockets
binding.
Raphael Cohn
Chief Architect, stormmq
Secretary, OASIS AMQP Standard
raphael.cohn@xxxxxxxxxxx
+44 7590 675 756
UK Office:
Hamblethorpe Farm, Crag Lane, Bradley BD20 9DB, North Yorkshire, United
Kingdom
Telephone: +44 845 3712 567
Registered office:
16 Anchor Street, Chelmsford, Essex, CM2 0JY, United Kingdom
StormMQ Limited is Registered in England and Wales under Company Number
07175657
StormMQ.com
On 16 March 2013 21:08, Roger Light <roger@xxxxxxxxxx>
wrote:
On Sat, Mar 16, 2013 at 9:02 PM, andypiperuk@xxxxxxxxx
<andypiperuk@xxxxxxxxx>
wrote:
>
> On Fri, Mar 15, 2013 at 6:07 PM, Raphael Cohn <raphael.cohn@xxxxxxxxxxx>
> wrote:
>>
>> We do need to register an IANA subprotocol for MQTT at some point
>
>
> The current IANA registration for MQTT is as follows:
>
> ibm-mqisdp 1883/udp # IBM MQSeries
SCADA
> ibm-mqisdp 1883/tcp # IBM MQSeries
SCADA
>
> did you mean something different?
I presume Raphael means a websocket subprotocol:
http://www.iana.org/assignments/websocket/websocket.xml
> I'm not sure who originally registered the
> IANA ports (AndySC possibly?) and it would be nice to have these renamed
to
> MQTT rather than the IBM-specific references.
It was Andy SC. I've mentioned the same thing before myself
:)
Cheers,
Roger
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
