Re: Streams and Concurrency

[dennison@telepath.com]

In article <76dn7b$a35@bgtnsc03.worldnet.att.net>,
  "James S. Rogers" <jimmaureenrogers@worldnet.att.net> wrote:
> Following is a modest example of what I mean about
> encapsulating a stream in a protected object.
>
> I believe this solution solves the interleaving problem.  The read and
> write operations will be atomic.  The write operation will not complete
> until all 'write operations for the tagged type complete.  The key is
> that the task calling the protected write and read operations is
> ignorant of the use of a stream.  No stream operations occur outside
> the protection of the protected type.

I see. You (probably Robert too) were talking about wrapping the client's
'Read and 'Write calls themselves. So what you have here is a multi-taksing
logging package, rather than a multitasking stream. I was thinking about a
pure stream implementation. There appears to be no way to write the stream
itself to handle this. Perhaps that's not as bad as I first thought it was...

But this solution only works for objects that are part of the same class
hiearchy. That's too restrictive. I'd want to be able to use any type. It
sounds like Tuck's generic suggestion is the way to go.

--
T.E.D.

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own