On Jul 13, 2006, at 11:55 AM, Jean-frederic Clere wrote:
With such an interface you assume only one process will access to
one slot... That is what the scoreboard allows.
Allowing updates from different proccesses on the same slot.
Should we have an ap_slot_read_look() and an ap_slot_unlock() for
that?
Having some external (or even internal) process update
a slot that isn't "its own" is dangerous. And the required
locking would be slow.
The scoreboard works as well as it does because
we restrict write only to the owner of the slot.
