Link42IconUsing LiveView to Handle Webhooks But now with LiveView when a webhook hits the server we can re-render on the server-side and push those changes to the client.
About every second or so the browser would send a request to the server to get the updated data. In a typical web application, without LiveView, common solutions are to either use websockets to push new data to client applications or have those applications poll the server. Mux is going to send webhooks to our server when relevant events happen. In the UI we show the user the streaming credentials and are now waiting for them to start streaming. Right here we have the perfect test case for LiveView.
Elixir phoenix liveview software#
As the user, you enter those streaming credentials into your mobile app or broadcast software and start streaming. When that channel is created, Snitch will give you RTMP streaming credentials (just like Twitch does). Under the hood, of course, we’re using Mux Live Streaming.įrom the user’s perspective, first you create a “channel”. The idea I had for an example app is Snitch, it’s like “Twitch,” but for snitches (put away your checkbooks potential investors). I decided to start playing around with LiveView to see what it’s capable of. At Mux we use Phoenix and Elixir to power our API. If you’re not familiar with Phoenix, it’s the fully-featured web framework for the Elixir programming language. Phoenix LiveView is a new experiment that allows developers to build rich, real-time user experiences with server-rendered HTML.
0 kommentar(er)
