From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue,  9 Jun 2009 14:49:44 -0400
From: Bhanu Nagendra Pisupati <bpisupat@cs.indiana.edu>
To: 9fans@9fans.net
Message-ID: <Pine.LNX.4.64.0906081807350.385@tank.cs.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: [9fans] critique of sockets API
Topicbox-Message-UUID: 07f27922-ead5-11e9-9d60-3106f5b1d025

Interesting read:
http://cacm.acm.org/magazines/2009/6/28495-whither-sockets/fulltext

If I am right, the filesystem based networking interface offered by Plan 9
has the three limitations discussed here:
* performance overhead: app requesting data from a socket typically needs
to perform 2 system calls (select/read or alt/read)
* lack of an "kernel up-call API": which allows the kernel to inform an
app each time network data is available
* hard to implement "multi homing" with support for multiple network
interfaces

Any thoughts/comments?

Thanks,
-Bhanu