M3rl1n-init
I would like to know if anyone knows how live view will effect the CDN and other caching mechanisms. I know and understand that the changes will be treated as dynamic in nature. This means that we will update the cache each time there is a change. If your CDN supports it then only the diff will be sent to the browser.
How does live view work with elm is another cquestion. I like the concept but I need to ensure I have elm components within my application as this simlified things. The problem is how these should be embeded and what is the best strangey.
I know that elm attached a runtime to the JS file. The runtime is delivared each and every time. The runtime is small but does this mean it will be sent for each and every compiler. I also know that we can not interact with the dom from with elm soI suspect issue with the UI system.
To sumurise:
LiveView when it comes to caching and rendering ?
Elm and working with liveview ?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
easco
LiveView would, by in large, be delivering HTML. That HTML might include hyperlinks (e.g. a link to an image) and the browser would have to fetch the associated content. If that content lived on a CDN (if the image was stored on a CDN) then the browser would fetch it from there.
Elm is a client-side framework for calculating and working with client-side generated HTML. If your HTML is generated client side then it would not be delivered via LiveView.
easco
Webpack has tools called ‘loaders’. A loader tells it what to do when it encounters a particular file. Usually you tell it to recognize files by regular expression patterns in the config. Your config would says something like “if you see an include for a file that ends in .elm, then use the elm loader”. The elm loader would compile the file and susbstitute the JavaScript.