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: Mint.HTTP — Mint v1.9.0
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, ex_ari/lib/ex_ari/http_client.ex at master · entropealabs/ex_ari · GitHub
and it’s usage here, ex_ari/lib/ex_ari/http/asterisk.ex at master · entropealabs/ex_ari · GitHub
and here
https://github.com/CityBaseInc/ex_ari_example/blob/master/lib/application.ex#L26
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.
Last Post!
entone
Sorry for the delay, was on vacation.
It’s not a trivial question, and actually something I meant to address. I just forgot to revisit the connection stuff once it was working ![]()
Thanks for the reminder, it is supposed to maintain one connection.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










