thojanssens1
Understanding the request reference `request_ref` in Mint
When calling Mint.HTTP.request/5, a request identifier request_ref is returned.
Then when streaming the responses with Mint.HTTP.stream/2, I need to wait for messages and make sure that the request reference inside the message received matches with the request reference that was returned by request/5. More can be read here: https://hexdocs.pm/mint/Mint.HTTP.html#stream/2-responses
I do not actually understand how the messages could include another request reference; I was thinking, maybe it can happen if I execute multiple times in parallel request/5 and stream responses; however I tried spawning multiple processes executing requests, but never I get a message with another request_ref.
How can I reproduce it?
Most Liked
NobbZ
Well, you can start many requests from the same process, all of them will have a unique ref. You can use it to collect individual replies into individual result sets.
entone
I’ve got a small client I wrote for the ex_ari library, you can check out the source here, https://github.com/CityBaseInc/ex_ari/blob/master/lib/ex_ari/http_client.ex
and it’s usage here, https://github.com/CityBaseInc/ex_ari/blob/master/lib/ex_ari/http/asterisk.ex
and here
entone
The model here, is we start one process per REST resource, and that process manages concurrent requests for that endpoint.
You could easily have one process manage all of your endpoints. But I didn’t want one hot resource to slow everything else down. For example, the Channel resource probably sees 80% more traffic than any other one.







