Search Results for "websocket client"

...Poxa uses gproc extensively to register websocket connections as channels. So, when a client subscribes for channel 'example-channel', the websocket connection (which is a elixir process) is "tagged" as {pusher, example-channel}. When a pusher event is triggered on the 'example-channel', every websocket matching the tag receives the event.

live_svelte bridges Phoenix LiveView with Svelte components, letting you blend server-driven UIs and client-side interactivity in a single application. It mounts Svelte components from HEEx templates and wires props and events through a small interop layer, so data flows cleanly between LiveView assigns and Svelte state. The integration supports dispatching client events back to LiveView and pushing updates down to the component without writing custom glue for every case. This makes it...

Phoenix LiveView is an Elixir library that enables rich, real-time user experiences by using server-rendered HTML over WebSockets, providing seamless dynamic interactivity without needing front-end JavaScript frameworks. It integrates deeply with Phoenix and ships by default in new Phoenix applications. LiveView brings a unified experience to building web applications. You no longer have to split work between client and server, across different toolings, layers, and abstractions. Instead,...

Phoenix is a high-performance, productive web development framework written in Elixir. It runs on the Erlang VM (BEAM). It is designed to support both traditional request/response web applications. It also supports real-time, soft-real-time applications via WebSockets, channels, PubSub, and presence features. Phoenix emphasizes fault tolerance, scalability, and developer productivity. It provides tools like code generators, LiveView integration, templating, routing, and a flexible plug...