Yeah the non-blocking interface has some fault tolerance benefits as
Brian mentioned. We are not quite far enough along to use it yet. I
think that we might need to extend it a bit, but I haven't looked at
it in enough detail to say how exactly at the moment.
So I would say for the moment l
I don't think so (in fact the bookkeeping overhead of the non-blocking
receive is a slight detriment).
Right now modex information is only exchanged during init and during
spawn/dynamics operations (and I do not see that changing at any point
soon). So I think the only use of the non-blocking rec
On Oct 8, 2007, at 11:55 AM, Andrew Friedley wrote:
Tim Prins wrote:
Hi,
I am working on implementing the RSL. Part of this is changing the
modex
to use the process attribute system in the RSL. I had designed this
system to to include a non-blocking interface.
However, I have looked again
Tim Prins wrote:
Hi,
I am working on implementing the RSL. Part of this is changing the modex
to use the process attribute system in the RSL. I had designed this
system to to include a non-blocking interface.
However, I have looked again and noticed that nobody is using the
non-blocking mod
