Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: 62.109.34.14 is neither permitted
 nor denied by domain of jens.rantil@telavox.se)
From: Jens Rantil <jens.rantil@telavox.se>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Date: Fri, 16 Sep 2011 13:02:38 +0200
Subject: SV: community of CouchDB developers in the Netherlands
Thread-Topic: community of CouchDB developers in the Netherlands
Thread-Index: Acx0RlW6azdS9EZQTD2urAXA2q9ybAAGYeYA
Message-ID: <850092711C09C042B93EC2F4F2E8B1E70276B1DF29@ex-mbx4.hosting.local>
References: 
 <CALtvvM9tsrocDBj8P1i4vgs7fWpR64Xx3KsnijeFHWi6+KjdOA@mail.gmail.com>
	<CAKmKYaChbG8sqP=jAeyW8VD4KeGombMVCkfVPCKMRjAt1YbV_A@mail.gmail.com>
	<CALtvvM9m04YLQmRXzUqWQeRN9XF5Ka_bkkiFUOexjfSruCGSkw@mail.gmail.com>
	<CAAL6JQjF4Lz=16NL37+UBeS4+=ON4cr-varMkVf9iehE=AXr1g@mail.gmail.com>
	<CALtvvM_N1WHkfW0sXwo=YRtqJNOvHoyO+Wp0_8YvVu=ymmEs7A@mail.gmail.com>
	<CAAL6JQge0oorK3oJjWEahoQKR89ZA_1FxWiMub5Uhx99KWvJiw@mail.gmail.com>
 <CALtvvM_T9oV2oq_TdOTktH30biRSH_wrJgPPnGQmJXKrDvXbPw@mail.gmail.com>
In-Reply-To: 
 <CALtvvM_T9oV2oq_TdOTktH30biRSH_wrJgPPnGQmJXKrDvXbPw@mail.gmail.com>
Accept-Language: en-US, sv-SE
Content-Language: sv-SE
acceptlanguage: en-US, sv-SE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Andrey,

If you would like to know more about how OTP (gen_servers etc.) work I can =
recommend "Erlang and OTP in Action". It gives you a very good introduction=
 to not just the language Erlang, but also OTP and design philosophies of E=
rlang.

Regards,
Jens

-----Ursprungligt meddelande-----
Fr=E5n: Andrey Somov [mailto:trophybase@googlemail.com]=20
Skickat: den 16 september 2011 09:57
Till: dev@couchdb.apache.org
=C4mne: Re: community of CouchDB developers in the Netherlands

Thank you Randall.
Even though I have read a lot about the gen_server  I still have a lot of d=
ifficulties to understand both the big picture and the small details of the=
 implementation.
That is why I was hoping to find someone who can guide me in the very begin=
ning.
In person it can be so much easier...
Apparently, here in the Netherlands Erlang is not that popular. (which is a=
lso an indication that it should be impossible to find a job with Erlang)

Cheers,
Andrey

On Thu, Sep 15, 2011 at 6:45 PM, Randall Leeds <randall.leeds@gmail.com>wro=
te:

> On Thu, Sep 15, 2011 at 05:38, Andrey Somov <trophybase@googlemail.com
> >wrote:
>
> > Thank you very much for your time and efforts.
> > It helped me to understand something but for each explanation I got=20
> > 10
> new
> > questions :)
> >
> > Just the first one.
> >
> > *>> open_async(Server, From, DbName, Filepath, Options) ->
> > >>    Parent =3D self(),
> > >>
> > >First, store the current process ID so it can be accessed later on,=20
> > >from
> a
> > >closure running in another process.*
> >
> > There is only one couch_server process. It is created like this:
> > gen_server:start_link({local, couch_server}, couch_server, [], []).
> >
> > As far as I understand it means that there is no need to remember=20
> > the process ID (Parent), and instead of gen_server:call(
> >                Parent, {open_result, DbName, Res, Options}, infinity
> >            ),
> >
> > we can use
> >
> > gen_server:call(
> >                couch_server, {open_result, DbName, Res, Options},
> infinity
> >            ),
> >
> > I have many more but to avoid misunderstanding I would propose to=20
> > stop here.
> > I will try to dig further myself.
> > When I have specific questions I will try to approach this list.
> >
> > Thank you !
> >
>
> Andrey,
>
> This is exactly right. Although, the 'safer' thing to do which makes=20
> refactoring easy is to use the special constant ?MODULE to refer to=20
> the name of the current module.
> More than one way to get things done :)
>