From an end-user's perspective: Yay! on all points.

Both client and server-side multithreading is a good idea if it is 
necessary. However, it would be nice to be able to limit the number of 
theads, especially server-side: if Xvnc spawns 24 (light) threads 
continuously on a HPC server, I am afraid it will have a negative impact 
on the running computations.

About this:
> General musings on VNC architecture:
>
> Even with the above, there are still fundamental problems with the VNC
> architecture in high-performance implementations like TigerVNC and
> TurboVNC.  The problem of all clients slowing down to the speed of the
> slowest client is a well-known phenomenon caused by a complex
> interaction between the speeds of the clients and the deferred update
> timer.  In a nutshell, what happens is that if any client's frame rate
> drops to less than 1 / (ping time to that client), then all clients will
> fall into lock-step.  This is worked around by ensuring that clients on
> slow networks use a sufficiently low JPEG quality to keep their frame
> rates above the required level, but it really points out how,
> ultimately, a lot of esoteric performance behavior could be eliminated
> simply by implementing a proper frame spoiling mechanism.  This would
> eliminate the need for the CU feature as well.
What about a client-side button which is able to 'pause' all other 
clients? And another button to resume the client again?

So, when you are at work, you have the high-speed setting, but at home 
(if you have the session at work still running), you can deceide to not 
send (high-speed network) updates to the other client.

Greetings,
Sebastiaan


------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to