Attributes | Values |
---|
has container
| |
Date Created
| |
maker
| |
described by
| |
Date Modified
| |
link
| |
id
| - 0218db84f3b9b1bf836e24c88e3eefba
|
content
| - Having two gen_servers call each other cyclically was one of the first dedakocls I ran into implementing Reia, a hybrid object/actor language for the Erlang VM. Reia uses gen_server as the basis of its objects, and as it guises gen_server calls in traditional obj.method(arg1, arg2...) style syntax it's easy to accidentally have two objects call each other cyclically.I believe we have a solution though: someone on the mailing list proposed a rather simple mechanism for cycle detection (by generating a unique ref for each call chain).Rather than deadlocking on cyclical calls, Reia objects will immediately crash when called cyclically. There's no need to depend on timeouts to detect the problem.
- Having two gen_servers call each other cyclically was one of the first dedakocls I ran into implementing Reia, a hybrid object/actor language for the Erlang VM. Reia uses gen_server as the basis of its objects, and as it guises gen_server calls in traditional obj.method(arg1, arg2...) style syntax it's easy to accidentally have two objects call each other cyclically.I believe we have a solution though: someone on the mailing list proposed a rather simple mechanism for cycle detection (by generating a unique ref for each call chain).Rather than deadlocking on cyclical calls, Reia objects will immediately crash when called cyclically. There's no need to depend on timeouts to detect the problem.<br />
|
reply of
| |
Title
| - Re:Developer Recruitment Exercise
|
is described using
| |
atom:source
| |
atom:updated
| |
atom:title
| - Re:Developer Recruitment Exercise
|
label
| - Re:Developer Recruitment Exercise
|
atom:published
| |
type
| |
is topic
of | |
is link
of | |
is has reply
of | |
is atom:contains
of | |
is atom:entry
of | |
is container of
of | |