From owner-freebsd-hackers Sat Feb 22 03:50:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA02417 for hackers-outgoing; Sat, 22 Feb 1997 03:50:55 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA02399 for ; Sat, 22 Feb 1997 03:50:50 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA22116 for hackers@FreeBSD.ORG; Sat, 22 Feb 1997 12:50:49 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id MAA06763; Sat, 22 Feb 1997 12:29:27 +0100 (MET) Message-ID: 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? References: <199702210119.RAA00608@lightside.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702210119.RAA00608@lightside.com>; from Jake Hamby on Feb 20, 1997 17:19:21 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. ;-)