Re: EventLoop.isCurrentThread() race condition

[Andrew Cagney <cagney at redhat dot com>]

Kris Van Hees wrote:
> I see that the way you "fixed" the test is functionally identical to the
> "hack" I use in TestMemorySpaceByteBuffer to work around this EventLoop
> problem.  I hope this hack is not meant to be the final solution to this
> race condition?  This really should be resolved in EventLoop, rather than
> introducing a hack to make this work, and potentially getting stuck with
> this problem popping up in other existing and future code.  Depending on
> side effects in what appears to be a basic query method is dangerous (as
> we can see from the issue with TestByteBuffer).
>
>   

We could explore ways of creating the event-loop so that the intent is 
dictated up-front; I'll put that on my to-do list.  The event-loop is 
due for another pass anyway.

Btw, the test you added for Memory transfers, that is to tickle the 
multi-byte transfer interface, right?

Andrew