On Fri, May 12, 2006 at 01:51:57PM -0700, Erik Nordmark wrote:
So my preference would be to deprecate them since what we really would
need is a n:m mapping table between process ids and transport endpoints.
Any other comments?
If not, how do we go about deprecating them?
On the
Le Jeudi 11 Mai 2006 09:30, vous avez écrit :
This assumes that one may use an ULA (IPv6) to reach a globally
routable (IPv6) address.
yes
In other words, that someone has introduced some kind
of NAT or transparent proxy in the middle.
no
it assumes that the routability domain of a
Le Samedi 13 Mai 2006 02:49, Perry Lorier a écrit :
How would this work as a nonblocking connect? A lot of network
services can't afford to block, they have other sockets to service.
Would it return an fd_set? maybe a poll array? Maybe it would
integrate with linux's epoll(), or freebsd's
It seems to me that having some process identified with a endpoint
(socket) has value. Yes, it may not be the actual process now using the
endpoint, but it still provides some meaningful information (such as the
process that originally created the endpoint).
I'd rather see the description change,
Messages | Bytes| Who
+--++--+
16.67% |6 | 21.09% |39775 | [EMAIL PROTECTED]
13.89% |5 | 12.55% |23667 | [EMAIL PROTECTED]
11.11% |4 | 13.78% |25993 | [EMAIL PROTECTED]
8.33% |3 | 7.55% |
