Re: Netowrk connectivity (was: segfault on font ...)

> On Tue, May 18, 2004 at 12:18:21AM +0000, xhook wrote:
> > Soon I'm going to do some work on y's tcp module, which seems to be
> > implemented in a very simple way now.
> 
> It's not particularly important given that module (and probably
> interface) is going to die, but I have to wonder what you have in
> mind; there's very little else it *could* do.

I don't see at least two basic things in current implementation:
1. handling of partial sends
2. SIGPIPE handler
It's only 5 minutes of work.
Might be I'm not right and you've already done it in some way i don't
see and don't know. Correct me please...

I don't think that it's a good idea to bury tcp driver, because unix
domain sockets forwarded via ssh DO NOT solve any problems. It won't
even solve a problem of tcp reset attack just because ssh uses tcp too.
As it's already said, tcp is great for network transparency. It's wide
spread and it will let to use Y under ms windows and other non-unix
systems.
Also I want to add that, by the time of final Y release every linux
distribution will have a kernel with hardened tcp stack and tcp reset
attack won't be such a great problem. 

So, I don't see the reason why tcp must be removed from Y.

Best wishes,
Dmitry Zhukov

p.s. BTW, how to switch libyc++ to use TCP instead of UDS?