Skip to content
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.

HTTP Path/Transport Update #149

Open
quartzjer opened this issue Mar 2, 2015 · 1 comment
Open

HTTP Path/Transport Update #149

quartzjer opened this issue Mar 2, 2015 · 1 comment
Labels
Milestone

Comments

@quartzjer
Copy link
Member

Right now the HTTP transport is HTTP/1.x and socket.io based, update the spec to include detecting/using HTTP/2.

Also research detecting/using CoAP as a fallback?

@quartzjer quartzjer added this to the IoT milestone Mar 2, 2015
@quartzjer quartzjer added the draft label Mar 6, 2015
@fd
Copy link
Contributor

fd commented Dec 21, 2015

Just some thoughts:

  • HTTP2 detection should be transparent
  • Server->Client data should be delivered via https://en.wikipedia.org/wiki/Server-sent_events
    • (Clients that don't support SSE should start long-polling)
  • Client->Server data should be delivered via POST requests (with the packets embeded in the form data as a base32 string).
    • When http2 is supported these requests will be multiplexed over one http2 connection (along with the SSE stream)
  • WebSockets are not very well supported and add allot of complexity. IMHO WebSockets should not be used.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants