[EMAIL PROTECTED] wrote:
the only chance to get rid of it, is to use unix domain socket (via -nolisten tcp) OR
to
add the option, to specify the interface bindings and be able to bind it to local
loopback
ONLY. I`d prefer the second one.
Why? What benefit does a TCP loopback connection provide over the Unix
domain socket (which is generally faster on most OS'es)?
ahhhh - btw - i see:
on http://www.tightvnc.com/changelog-unix.html
2001-01-17 01:55 const
Xvnc/programs/Xserver/hw/vnc/: init.c, rfb.h, sockets.c: Support for Xvnc -interface
option added (patch from Tim Waught).
feature seems to be in tightvnc already - so maybe we need just some code transfer
(since vnc is xfree86
based) ? ;)
Only if the original author of the tightvnc changes agrees to
distribute under the X license instead of tightvnc's GPL.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - Sun Software Group
User Experience Engineering: G11N: X Window System
