spawn without linking?
Wed Apr 21 05:20:27 CEST 2004
Actually, it is that hard to do... the OTP behaviors offer lots
of well tested/debugging implementations which handle the border
cases extremely well. Which a naive quick implementation using
just the basic spawn_link/* and trap_exit won't get quite right on
the first few tries.
OTP rocks for that reason alone... but yea, gen_server isn't the
most "Erlang" way to write a server, but its the Erlang/OTP way.
Dustin Sallings <> wrote:
> On Apr 20, 2004, at 19:09, Vance Shipley wrote:
> [lots of really useful information for which I'm grateful]
> >The real solution is to use the design patterns in OTP. You need a
> >top level supervisor which starts children and restarts them when
> >necessary. The SASL application runs to handle error_reports,
> >crash_reports and progress messages. Your server processes are
> >instances of gen_server behaviours. You start the application
> >using application:start/1. Using this framework you will create
> >more resilient applications without having to think too hard about
> I was going through the course thing and trying to understand
> process relationships and stuff. Even with this, it doesn't seem *that*
> hard to do it manually, but I'm all for better ways to do things.
More information about the erlang-questions