How we got to LiveView

Re:How we got to LiveView by staticelf on Wednesday September 22, 2021 @04:31PM (#28621380)

Are you guys looking into the Web Transport protocol for the future? Right now you have to tunnel the websocket connections over http2 and it will probably be the same for http3 afaik.

I know there is this work in progress (https://w3c.github.io/webtransport/) and websockets are probably fine for a long time but sooner or later (unless there is an update to websockets) it will probably be faster to just do normal http requests and listen on server sent events.

What are your thoughts for Liveview for the future? Will it forever stay on websockets or would you be open to change the underlying technology if / when new stuff becomes available?

[ Parent | on HN ]

Re:How we got to LiveView by chrismccord on Wednesday September 22, 2021 @11:42PM (#28624994)

Phoenix Channels (which LiveView is built on) is transport agnostic, so as soon as we can open a pipe from the browser's JS environment, and listen on the server, we could have a `Phoenix.Transports.WebTransport`. All the existing user-land code and LV apis remain unchanged :)

[ Parent | on HN ]

Re:How we got to LiveView by staticelf on Thursday September 23, 2021 @03:21AM (#28626173)

That is something I suspected. When I first saw your talk about LiveView on youtube my mind was completely blown away.

It is such an awesome technology.

[ Parent | on HN ]