preserving message boundaries on named pipes - System V

[David F. Carlson]

> In article <571 at lehi3b15.csee.Lehigh.EDU> murrey at lehi3b15.csee.Lehigh.EDU (Erik Murrey) writes:
 >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?  
 
Although inefficient and contrived, if limits.h has PIPE_BUF == PIPE_MAX
and the reader and writer used *ONLY* that length, each read would
be an atomic message with no magic cookies required.


-- 
David F. Carlson, Micropen, Inc.
micropen!dave at ee.rochester.edu

"The faster I go, the behinder I get." --Lewis Carroll