[Seaside] Serving files
Jason Johnson
jbjohns at libsource.com
Fri Oct 13 17:07:21 UTC 2006
David Shaffer wrote:
> tim Rowledge wrote:
>>
>> On 11-Oct-06, at 5:10 AM, David Shaffer wrote:
>>
>> Assuming I understand 'tread safe' in same way that you mean it, that
>> isn't strictly correct. The problem is that the squeak model use
>> separate positioning and read/writing calls. Thus is is quite
>> possible (been there....) to have two processes referring to the same
>> file and get
>> procA -> position: a
>> procB -> position: b
>> procA -> read from position (which I thought was a!)
>> boom.
>>
> I thought my meaning was the obvious one but now that I hear yours I'd
> agree that I was wrong. So...(let's hope the second try is a charm)
>
> Just a point of clarification: file I/O on a single Stream is not
> thread safe
I know of no languages that are. If two processes are sharing the same
data structure, then that will always have race conditions, unless every
access is blocked by a Mutex (which, of course, you don't want).
More information about the Seaside
mailing list