preserving message boundaries on named pipes - System V

[Erik Murrey]

System V.3.1 Unix

Is it possible to preserve message boundaries on named pipes under
System V?  For instance, if a process sends two separate messages (via
two write()'s) down a named pipe, how can the receiver read those as
two separate messages?  It seems that right now, if the reading
process unblocks after both writes have completed, then it gets *both*
messages in one read.

I really don't wan't to muck with terminating null characters, and
the like...

... Erik

-- 
Erik Murrey
Lehigh University
murrey at csee.Lehigh.EDU
erik at mpx.com