Date: Sat, 22 Feb 1997 12:29:27 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Alternatives to SYSV IPC? Message-ID: <Mutt.19970222122927.j@uriah.heep.sax.de> In-Reply-To: <199702210119.RAA00608@lightside.com>; from Jake Hamby on Feb 20, 1997 17:19:21 -0800 References: <199702210119.RAA00608@lightside.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Jake Hamby wrote: > ..., but what about messages? Sockets could be used, but they just > provide an arbitrary stream of bytes, not discrete messages. FIFOs > have the same problem, and pollute the filename space (I have the > same problem with using mmap() for shared memory). What else than `an arbitrary stream of bytes' is a message? Define your message to be a structure, with a length and type field at the beginning, and type-dependant data following. FIFOs (or local-domain sockets) don't pollute the name space more than SysV msgs did. Remember, all that SYSVIPC created a second (and 3rd etc.) namespace, with an inconsitent set of programs to handle them, and even inconsistent attributes, IIRC. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970222122927.j>