Actually, while we're at this level I'd like to bolt on another
thought / query - these were my words;
> But after sitting on the idea for a couple of days I actually came
> to the same conclusion as Manu did in the last message. I.e.
> without docco I have been writing to what seems to work, and
> in my 2009 code (I saw last night) a "mkdir" wind followed by "create"
> code in the same function - which I believe, now, is probably a
> race condition (because of the threaded/async structure forced
> through the wind/call macro model).
But they include an assumption.
The query is: are async writes and reads sequential? The
two specific cases are;
1) Are all reads that are initiated in time after a write
guaranteed to occur after that write has taken affect?
2) Are all writes that are initiated in time after a write (x)
guaranteed to occur after that write (x) has taken
affect?
I could also appreciate that there may be a difference between
the top/user layer view and the xlator internals .. if there is then
can you please include that view in the explanation?
Cheers,
--
Ian Latter
Late night coder ..
http://midnightcode.org/
