On Mon, 17 Dec 2007, Ludovico Gardenghi wrote:
On Mon, Dec 17, 2007 at 04:10:19AM -0800, [EMAIL PROTECTED] wrote:
if you are talking network connections between virtual systems, then the
exiting tap interfaces would seem to do everything you are looking for. you
can add them to bridges, route
On Mon, Dec 17, 2007 at 04:10:19AM -0800, [EMAIL PROTECTED] wrote:
> if you are talking network connections between virtual systems, then the
> exiting tap interfaces would seem to do everything you are looking for. you
> can add them to bridges, route between them, filter traffic between them
On Mon, 17 Dec 2007, Ludovico Gardenghi wrote:
On Mon, Dec 17, 2007 at 03:31:48AM -0800, [EMAIL PROTECTED] wrote:
wouldn't it be better to just add the ability for multiple writers to send
to the same pipe, and then have all of them splice into the output of that
pipe? this would give the same
On Mon, Dec 17, 2007 at 03:31:48AM -0800, [EMAIL PROTECTED] wrote:
> wouldn't it be better to just add the ability for multiple writers to send
> to the same pipe, and then have all of them splice into the output of that
> pipe? this would give the same data-agnostic communication that you are
On Mon, 17 Dec 2007, Renzo Davoli wrote:
Inter Process Networking (PATCH):
1. WHAT IS IPN?
---
IPN is a new address family designed for one-to-many, many-to-many and
peer-to-peer communication among processes.
Berkeley sockets have been designed for client-server or point-to-point
Inter Process Networking (PATCH):
This patch adds a new address family for inter process communication.
AF_IPN: inter process networking, i.e. multipoint,
multicast/broadcast communication among processes (and networks).
Contents of this document:
1. What is IPN?
2. Why IPN?
2.1 Why