From: "William Hooper" <[EMAIL PROTECTED]> Date: Tue, 12 Nov 2002 08:22:32 -0500
So you would have the VNC programmers not only add this component, but also port it to the different platforms the VNC runs on, and try to keep up with new versions/security of someone else's code?
Sound support need not use a particular implementation. It might be more efficient than reinventing the wheel, but it's not a necessity.
Not to mention how "big" VNC might get adding this code (I haven't looked so I don't know how "big" nasd would be).
So it's an open issue until somebody actually determines the size implications.
Just saying "Add sound support" doesn't make it easy. I for one agree with the fact VNC does it's one thing well, why try to tack on more things to make it more complex?
If the "one thing" is remoting the human-computer interface, VNC lacks sound support, which is an integral part of the HCI, so cannot be said to do that well. If the "one thing" is mere remote frame buffer display, then you're effectively arguing that mouse and keyboard support should be ripped out to reduce size. Is that really your opinion? Some other requests for added features which are frequently proposed (e.g. file transfer, printing) are unrelated to the HCI; moreover, there are readily available auxiliary programs (e.g. ftp, lpr/lpd) which provide those features. The same cannot be said for sound support. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
