Cumulative and always growing data – chat applications, logs, and similar can be built with LiveView but currently you have to keep in the server a copy of all messages shown in the client as there is no append/prepend operation.Page and data navigation – such as navigating between pages, pagination, etc can be built with LiveView but currently you will lose the back/forward button, and the ability to link to pages as you navigate.Once the state changes, LiveView will re-render the relevant parts of its HTML template and push it to the browser, which updates itself in the most efficient manner. Events in LiveView are regular messages which may cause changes to its state. LiveView provides rich, real-time user experiences with server-rendered HTML. Pubsub: ,įunctions include (broadcast, subscribe, unsubcribe)ĭo I need to unsubscribe? Phoenix.LiveView Used internally by Channels for pubsub broadcast but also provides an API for direct usage.Ĭan be used with Redis or Distributed Elixir (PG2), configured in the endpoint (config.exs): config :myapp, MyappWeb.Endpoint, to host web specific configuration for your applicationįront-end to Phoenix pubsub layer.to define an initial plug pipeline for requests to pass through.to provide a wrapper for starting and stopping the endpoint as part of a supervision tree.Overall, an endpoint has three responsibilities: It is also the interface your application provides to the underlying web servers. The endpoint is the boundary where all requests to your web application start. _from(self(), "event", payload) Phoenix.Endpoint The Endpoint docs list various broadcast functions, yet I can either one: _from(Myapp.PubSub, self(), "event", payload) the following two lines do the same thing (Myapp.PubSub, this point, Phoenix.PubSub is not even a module in the docs, whereas it is in previous versions. At first glance, there appears to be overlap.Į.g.
0 kommentar(er)
