One of the things that attracted me to Erlang in the first place is t开发者_C百科he Actor model; the idea that different processes run concurrently and interact via asynchronous messaging.
In this example, the author avoids a deadlock situation by doing: self() ! {start_worker_supervisor, Sup, MFA}
when implementing a supervisor.. If, in the supervisor module, I do something like init([_]) -> {ok, {{one_for_one, 5, 60},
I\'m currently in a project making a gameserver. Every player is supposed have an own process with gen_fsm behavior. To start gen_fsm with start/3 we need a unique atom, currently we use make_ref() an
I\'m trying to understand what\'s happening here: I have a supervisor that is cyclically restarting one client without triggering the MaxR, MaxT mechanism.The client just crashes slowly enough never
I am struggling a little coming to grips with the OTP development model as I convert some code into an OTP app.
I try to write application to my Erlang program. I have test_app.erl: -module(test_app). -behaviour(application).
How do you organize your erlang workflow? I\'m learning some Erlang now and I\'m using Rebar, recompiling, rebuilding and restarting an entire release (I\'m开发者_如何学运维 trying to keep things OTP\
I have read one of erlang\'s biggest adopters is the telecom industry.I\'m assuming that they use it to send binary data between their nodes and provide for easy redundancy, efficiency, and parallelis
I am working over soluti开发者_StackOverflow中文版on to a problem, which requires changes in one of the functions of module gb_trees.
加载中,请稍侯......