Open mattheworiordan opened 5 years ago
➤ Tony Bedford commented:
The knowledge base article specifically lists protocols for:
“Our +Javascript browser library+ ( https://github.com/ably/ably-js ) will always choose the best transport available based on the browser and connection available.“
Yes, there other transports available such as:
We have these in the main documentation. We also have a protocols page:
But I wonder if the article was specifically about what transport the Ably client library SDKs use? They can't use MQTT for example.
Assigning to Mark Cox-Smith to decide whether the knowledge base article needs updating or expanding.
I wonder if the article was specifically about what transport the Ably client library SDKs use? They can't use MQTT for example.
ably-js has a number of transports implemented internally that it can use: websockets, xhr-streaming, xhr-polliing, comet. This is what it's talking about. In all cases, the Ably native protocol runs on top. So it's different from MQTT, SSE, which I would describe as different protocols, not different transports.
See https://support.ably.io/support/solutions/articles/3000044831-which-transports-are-supported-.
If someone searches for Ably XHR for example, they are taken here. Yet XHR and SSE is supported by Ably directly, so is MQTT etc. Should we update the article so that it's clear these are Ably Realtime SDK transports, but we support other transports and protocols directly, through the adapters.
┆Issue is synchronized with this Jira Task by Unito