denna
Send_later to Agent
I like to make use of Process.send_later to send a message to an Agent.
When I understand this tutorial right than one needs to implement handle_info to handle the message send by send_after. Agent doesn’t implement handle_info. Only gen_server does so.
As an example one could use the counter from the documentation:
defmodule Counter do
use Agent
def start_link(initial_value) do
Agent.start_link(fn -> initial_value end, name: __MODULE__)
end
def value do
Agent.get(__MODULE__, & &1)
end
def increment do
Agent.update(__MODULE__, &(&1 + 1))
end
end
Counter.start_link(1)
Process.send_after(Counter,:increment,1000)
Most Liked
hauleth
Agent is thin wrapper over GenServer, so the performance should be similar.
And your example using GenServer will not be much more complex:
defmodule Counter do
use GenServer
def start_link(initial_value) do
GenServer.start_link(__MODULE__, initial_value, name: __MODULE__)
end
def value, do: GenServer.call(__MODULE__, :get)
def increment, do: GenServer.call(__MODULE__, :inc)
@impl true
def init(value), do: {:ok, value}
@impl true
def handle_call(:inc, state), do: {:reply, :ok, state + 1}
def handle_call(:get, state), do: {:reply, state, state}
end
kokolegorille
Many don’t use Agent (and prefer GenServer), and many don’t use :timer library (and prefer Process.send_after, or similar) 
http://erlang.org/doc/efficiency_guide/commoncaveats.html
This is something You might learn from experience.
hauleth
Just don’t use Agent if you want to handle your own messages.
amnu3387
I think that’s what @hauleth is saying, if you need to receive messages on the Agent, then it’s not the right thing to use.
There’s several abstractions already written in both erlang and elixir and they all have a sort of “utility field”.
Agents are for keeping/retrieving state. GenServers are generic server interfaces, so they’re modelled as a behaviour that you can customise to handle your own message needs.
They can also do a slight impersonation of a state machine, but if you need actual state machine semantics, timeouts, stepped flows, etc then probably it’s easier to write a proper gen_statem which is an abstracted behaviour for that exact thing instead of shoehorning that into a gen_server, Tasks are for doing something and exiting, and so on.
If you need your Agent to receive messages and handle them then you’re either looking at gen_server or writing your own simple process to handle it (usually you’ll want the gen_server as its interface handles a lot of things for you)
hauleth
You send functions as a messages in Agent case. So if it is indeed true (I highly doubt that if these messages are on local machine) then GenServer will be more performant one, as it send just simple atoms.







