Databases
StackOverflow2013
Postsdbo
POHow to structure an Erlang OTP UDP server
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to structure an Erlang OTP UDP server
    primarykey
    data
    text
    <p>I am just reading <em>Manning's Erlang &amp; OTP In Action</em>. Very good book, I think. It contains a nice TCP server example but I'd like to write a UDP server. This is how I structured my app so far.</p> <pre><code>my_app % app behaviour |-- my_sup % root supervisor |-- my_server.erl % gen_server to open UDP connection and dispatch |-- my_worker_sup % simple_one_to_one supervisor to start workers |-- my_worker_server % gen_server worker </code></pre> <p>So, <code>my_app</code> starts <code>my_sup</code>, which in turn starts <code>my_worker_sup</code> and <code>my_server</code>. The UDP connection is opened in <code>my_server</code> in active mode such that <code>handle_info/2</code> is invoked on each new UDP message in response to which I call <code>my_worker_sup:start_child/2</code> to pass the message to a new worker process for processing. (The last call to <code>start_child/2</code> is in fact, as per the book's recommendation, wrapped in an API function to hide some of the details, but this is essentially what happens.)</p> <p>Am I suffering from OTP fever? Should the <code>my_worker_server</code> really implement the gen_server behaviour? Do I need <code>my_worker_sup</code> at all?</p> <p>I set it up in like this so that I can use <code>my_worker_sup</code> as a factory via the <code>start_child/2</code> call but I only use the worker's <code>init/1</code> and <code>handle_info(timeout,State)</code> functions to first setup state and then to process the message before shutting the worker down.</p> <p>Should I just spawn the worker directly? Is another behaviour better suited, perhaps?</p> <p>Thanks, HC</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UShcvst
    1. UShcvst
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to structure an Erlang OTP UDP server
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to structure an Erlang OTP UDP server
      1. USMuzaaya Joshua
      1. VTFavorite
    3. VO
      singulars
      1. POHow to structure an Erlang OTP UDP server
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think I might have found the answer to how to fit the worker into OTP as a 'special process' here http://www.erlang.org/doc/design_principles/spec_proc.html#id72749
      singulars
      1. POHow to structure an Erlang OTP UDP server
      1. UShcvst
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload