[erlang-questions] How to transform a classical code in worker process ?

[Gamoto]

Steve,
No, I don't wait for an "off the shelf" solution. When I read some other answers I think my request was realistic.
You are one partisan of the "RTFM phylosophy" probably and I respect your choice. It's not mine. I think we progress by sharing
knowledge. For me the Bob's code is still difficult to understand because I have not a long experience with Erlang. 
I read the OTP introduction, the notions of application, supervisor, etc. but I don't understand sometime the "why". Why does this guy
choose this solution and not this one, why gen_server and not gen_tcp, why supervisor_bridge and not supervisor, etc, etc.
And the answers of these "why" are not in books, there are in the mind of the people who have experience as probably yourself.
Don't blame me. I want to learn but surely by using a personal method you don't share.
Regards,
John

>Hi John,
>
>I appreciate that it would be nice for you if someone were to sit down 
>and write out the pseudocode for you, but I suspect that anybody who is 
>competent to answer would simply not have the time to do it. Thus, I 
>think your request is a little unrealistic.
>
>Bob's code is easy enough to follow, and it's good practice to learn to 
>read other people's code as so much open source stuff has little to no 
>documentation. It's also very useful if you are unsure of what exactly a 
>library function does from the docs -- you can just go into the module 
>and check for yourself.
>
>In your case, I'd probably suggest that you read the OTP introduction in 
>the erlang docs first though to get a good grasp on how OTP applications 
>are structured in erlang, and to get a feel for the entire rationale 
>behind OTP. This I believe is the part of the story that you are 
>currently missing.
>
>Regards,
>Steve
>
>
>Gamoto wrote:
>> Hi Steve,
>> Exactly what I didn't expected as answer ...
>> John
>> 
>> 
>