kostonstyle
Hi all
I have following module that implement GenServer, the code is from book elixir in action.
defmodule Todo.DatabaseWorker do
use GenServer
def start_link(db_folder, worker_id) do
IO.puts "Starting database worker #{worker_id}"
GenServer.start_link(
__MODULE__, db_folder,
name: via_tuple(worker_id)
)
end
defp via_tuple(worker_id) do
{:via, Todo.ProcessRegistry, {:database_worker, worker_id}}
end
end
What I do not understand is the name parameter in the start_link function. What does it mean, why the function via_tuple function return a tuple?
Thanks
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
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.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
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)
hubertlepicki
Read this, I blogged about namig processes earlier today:
In your example, it’s slightly more complicted scenario, where you are using third party registry
Todo.ProcessRegistry. Read this (after you read above):https://m.alphasights.com/process-registry-in-elixir-a-practical-example-4500ee7c0dcc#.k4zo7xjho
Qqwy
When normally (without using the
name:option) creating a GenServer, the only way to refer to it, is by its Process ID (PID).In most simple cases, this is good enough. However, in some cases it is annoying that there isn’t a different alias you can refer to, which means you’ll end up passing a list of PIDs around all over your application.
So instead, it is possible to register a process under a name, which is then stored globally (for the current node!) in Erlang. This means that one can refer to the process by using that name (as well as by its PID). This is often used when you only ever need a single process doing a certain kind. It is very common to have constructs like
name: __MODULE__, which means that you only want a single GenServer to run using the code in the current module.There are a few ways to specify a name other than an atom. @msambarino wrote a great explanation here that goes into more detail.
EDIT: Heh, @hubertlepicki was just a second quicker than I. Great blog post!
kostonstyle
@hubertlepicki and @Qqwy thanks so much for help. The article process registry in very nice.
Thanks very much guys