News for hackers. Stuff that matters.

A comment on Server-sent events, WebSockets, and HTTP. Parent comment

Re:Server-sent events, WebSockets, and HTTP by mmzeeman on Sunday February 20, 2022 @10:23AM (#30406396)
MQTT is a proven protocol. It's design started started more than 20 years ago. The protocol was designed to be easy to implement. It is simple to implement if you want. There are multiple brokers, and client libraries available. So why invent a new protocol, when an open, standardised protocol already exists.

Open pages in a browser are not that different from IoT devices.

[ Parent | on HN ]
Re:Server-sent events, WebSockets, and HTTP by musingsole on Sunday February 20, 2022 @11:52AM (#30407072)
> So why invent a new protocol, when an open, standardised protocol already exists.

Because despite being a dinosaur, it still only has middling adoption. It exists in a particular niche of a particular niche of computing.

HTTP, in contrast, is English to MQTT's German. One is just infinitely more common and accessible to the majority of the world. So, if you're serious, use it.

[ Parent | on HN ]
Re:Server-sent events, WebSockets, and HTTP by mmzeeman on Monday February 21, 2022 @06:16AM (#30414448)
There is no efficient pub/sub functionality in HTTP.
[ Parent | on HN ]
Re:Server-sent events, WebSockets, and HTTP by musingsole on Monday February 21, 2022 @09:07AM (#30416005)
https://duckduckgo.com/?q=websockets+pub%2Fsub&t=brave&ia=we...
[ Parent | on HN ]
Re:Server-sent events, WebSockets, and HTTP by mmzeeman on Wednesday February 23, 2022 @07:57AM (#30440465)
That is an non-standardised DIY pub/sub protocol over a websocket.
[ Parent | on HN ]
Re:Server-sent events, WebSockets, and HTTP by musingsole on Wednesday February 23, 2022 @01:25PM (#30444452)
You asked for pub/sub functionality over HTTP. Pub/sub implemented on WebSockets is just that.
[ Parent | on HN ]