Local Shared Objects and multiple SWFs: mutexes necessary?

Question

I will have multiple SWFs on a single web page, each reading
and writing the same SharedObject, which may be up to 100K in size.
Will I need to create some sort of mutex scheme to ensure that one
SWF isn't writing while another is reading, or do all SWFs on a
page essentially run as a single-threaded application?

Answer 1

>1) I don't think a SharedObject.flush is synchronous.
I believe it is, as long as you're not attempting to write
more data than the user has set for the Local Storage limit.
http://livedocs.adobe.com/flex/3/langref/flash/net/SharedObject.html#flush()
You'll note that flush is described this way: "Immediately
writes a locally persistent shared object to a local file", and if
it returns "SharedObjectFlushStatus.FLUSHED" that means that "The
shared object has been successfully written to a file on the local
disk". So I'd say that the normal operation of flush() is
synchronous. However, the SharedObjectFlushStatus.PENDING state
means that we've exceeded the limit set by the user, and are
waiting for them to allow or disallow it. I believe (strongly) that
that's the only case in which a netStatus event is sent.
Do you read this differently?
As far as multiple SWFs running as cooperative or preemptive
multitasking processes, I'd really like to know the answer, but it
probably doesn't matter. The more I read and think about this, the
more it seems to me that Adobe has to prevent simultaneous reads
and writes to a single Shared Object from taking place, as one use
of it that I've read about is to share data between SWFs. For
example:
http://www.devarticles.com/c/a/Flash/Communication-and-Security-with-the-Flash-Communicati on-Server/1/