nathanl
The Slipstream docs have a section on retries for establishing a connection.
But I don’t see anything about retries for messages. The docs for push/5 show using handle_reply/3 to handle an ack, but suppose an ack never comes, or takes too long to come. I think that could happen if:
- The server had a bug and lost the message
- The server channel crashed
- The TCP retries timed out and the connection crashed
I think in cases 2 and 3 some kind of error would be raised. But in any case, am I correct in assuming that the answer for message-level retries is “roll your own, according to your needs”?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #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.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
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!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
nathanl
@the-mikedavis
the-mikedavis
Yeah, retries are only built in for reconnecting. I was trying to mirror how Phoenix’s JavaScript client API works with that reconnection functionality. I don’t believe there’s anything built into the Phoenix Channel protocol for retrying messages - that should be built on top of
pushnathanl
That makes sense; each application may have different requirements for retrying messages. Thanks for confirming.