(02-26-2023, 04:03 AM)hamei Wrote: what you were doing that none of these methods was "enjoyable" ?
They all by-and-large functioned, and on simple webpages rdesktop and VNC were actually pretty usable, but the problems came mostly with high-res video, websites with fullscreen image/video backgrounds, smooth scrolling, animated content, and "web app" UIs - anything that really stressed the decompression and fullscreen/full-window bitmap drawing parts of the client. In these cases, it functioned, and I suppose would have been better if you had to use a site that didn't work at all on any native browser, but it was very very noticeably slow, and I didn't want to sell a piece of hardware that relied on software that was frustrating to use on the type of bitmap-heavy content that makes up a large fraction of modern websites.
The DFRD client, it's worth noting, is much less content-dependent than a lot of other remote desktop systems. There is currently no support for partial refresh - every frame is sent and drawn in full and independent of any other frame. Decompression performance with SLIC is only mildly dependent on image compressibility. The only part that depends on image complexity is how long it takes to receive the frame over the network, and the impact of that could be reduced with some pipelining in the client. I have tested with both simpler text content, and heavier video/full-frame scrolling image content, and the difference is mild - perhaps dropping to 30 fps in a configuration where lighter content would do 40.
=