nathanl

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:

  1. The server had a bug and lost the message
  2. The server channel crashed
  3. 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”?

Showing Posts 1 to 3

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 push

nathanl

nathanl OP

That makes sense; each application may have different requirements for retrying messages. Thanks for confirming.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews