kminevskiy
Hi,
I started building an app that uses Phoenix channels and was wondering what’s the right (or the most appropriate) way to maintain channel subscription. By default, channel subscription is closed after 60 seconds. I’m not using the built-in phoenix.js library - instead, it’s a native browser websocket API.
I found one pretty old example where pings are being sent by the server after the client “joins” the channel. However, as far as I understand, the way “keepalive” is handled right now (new-ish versions of Phoenix) is by resubscribing to the channel that sent the “close” event. Is this correct? If so, is that the appropriate way to handle it if I’m not using the standard phoenix.js library?
Thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #elixirconf-us
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync. Next: ElixirConf EU 2027
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
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!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
OvermindDL1
Channels are a higher level above websockets, it has a heartbeat and a specific format. If you want to use raw websockets you should just use a cowboy websocket with phoenix instead of channels.
If you really want to use the channel API then you’ll basically be recreating the phoenix.js library, so should just use it.
kminevskiy
Thanks for explanation!
It makes sense now - I’m not the one working on the front-end portion (it’s a separate app that consumes my backend API), so I wasn’t sure how to interact with my API using non-phoenix.js front-end. Now all’s clear