"Erlichmen, Shay" wrote:
>
> Wow, our company does the same thing, and we discover the VNC is not very
> efficient with multiple connections, so for that propose we wrote VNCProxy.
> The proxy connects to the VNC server with a single connection and tunnel the
> data stream to its clients. I guess that we can make the source code for it
> available soon.
<...>
So how do you handle requests for frame buffer updates?
Do all clients connected to the proxy get their updates without doing
requests of their own (maybe the proxy just drops these)? If so, have
you taken possible congestion problems with this into account (maybe by
letting the proxy handle these requests, without forwarding them to the
server?)
Or are all connected clients doing their own requests for frame buffer
updates, and are these all tunneled in the 1 connection form the proxy
to the server? (Well, that would seem a bit compilicated.)
Just curious.
--
Harmen
http://www1.tip.nl/~t515027/brandgang/
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
