🚀 go-pugleaf

I've got a few (possibly simple) questions about passing data in
messages between 
threads in the same task:

I'd like to set up a communication path intended to be between
two threads and involving potentially large amounts of data.
I'd expect to use ports to do this, cause I'd like to be able
to handle the case where the treads are NOT in the same address
space (NOT in same task).  In this case I expect that the
data is actually copied around. (is it?)

Now, without changing the send/receive code in my threads,
I'd like to be able to also do this for the case where the
two threads ARE in the same task.  And finally, the question: does
this mean that the data is NOT copied around? -- that no data
is actually going into/out-of a port?

You see, I want to have the o/s make it be effecient when
that's possible, or to have it NOT be effecient when that's
necessary, WITHOUT MY HAVING TO hard-wire this into my code.

To change the subject to OSF/1, are C threads considered part of the "standard
Mach interface" in OSF/1, or is it strictly the POSIX Threads Extension
standard
that will be supported in OSF/1.

Thanks.  I apologize if these topics have been discussed before or are
inappropriate to thiis newsgroup.

-- dan
******************************************************************************
* Daniel Green  green@daniel.b17a.ingr.com|_   /| UUCP: ~!uunet!ingr!greendl *
* Intergraph Corporation Mail Stop IW17A1 |\'o.O` Internet: greendl@ingr.com *
* Huntsville, AL  35894-0001 (205)730-1770|=(___)= "Ack Thippfft!" -- Bill   *
**********************************************U*******************************