| |||||||||||||
Bad and complex architectureBad and complex architecturePosted Jul 25, 2009 16:52 UTC (Sat) by lab (subscriber, #51153)In reply to: Bad and complex architecture by nix Parent article: Google releases Neatx NX server
Yes, I can confirm this, and it's the same problem with RDP (MS remote desktop). Most things work fine, but it seems that applications implementing their own GUI drawing routines, rather than using native widgets, causes any remote desktop implementation relying on bitmap transfers to come to a grinding halt. A classic example is Java based Swing, and as mentioned modern version of Oracle Forms, which is rendered as Java applets, probably using Swing libraries.
How does technology like pure X or NX fare with these type of apps?
(Log in to post comments)
Bad and complex architecture Posted Jul 25, 2009 17:12 UTC (Sat) by astrand (guest, #4908) [Link]
Actually, I claim the the opposite is true: VNC can and does deal with bad applications good. This means that Swing-based Java applications works much better with VNC than with NX. Every time I've tested NX, I tried a Java based application and confirmed the bad performance.
From a technical viewpoint, Xvnc does (by default) pixel-by-pixel comparisons on the framebuffer. So unless you have explicitly disabled this (-CompareFB=0), or have some strange client, I really don't understand why you are experiencing this behaviour.
It's better to have half a cake then no cake at all Posted Jul 27, 2009 6:02 UTC (Mon) by khim (subscriber, #9252) [Link] Every time I've tested NX, I tried a Java based application and confirmed the bad performance. Don't use such applications then. Sure, badly-written applications are unusable with NX - and most Java-based applications are pigs in regard to any and all resources. But with VNC all applications are equally unusable!
|
|||||||||||||