| |||||||||||||
You betray your ignorance of waylandYou betray your ignorance of waylandPosted May 28, 2012 5:52 UTC (Mon) by butlerm (subscriber, #13312)In reply to: You betray your ignorance of wayland by raven667 Parent article: Announcing printerd
RDP is based on T.128, which has the usual set of rendering operations, font and image caching, and so on. I understand that ICA is similar, and so is SPICE. Of course actual implementations may rely more on bitmap updates then the supported rendering commands these days for relatively obvious reasons.
(Log in to post comments)
You betray your ignorance of wayland Posted May 28, 2012 6:43 UTC (Mon) by raven667 (subscriber, #5198) [Link]
> RDP is based on T.128
I'm not sure if that's the chicken or the egg, these protocols (RDP, ICA) have been deployed for more than 20 years and I'm not sure that the standards you references aren't just ex post facto documentation of existing practice.
> the usual set of rendering operations, font and image caching, and so on
One more thing to point out is that all the protocols I listed are add-ons to an existing system (mostly MS Windows) that isn't designed around remoting applications and so has to integrate with an infrastructure designed around local display, the same kind of problems that would need to be solved to remote native Wayland applications.
The methods for local display and remote display have little relation to one another and I think experience has shown that this is a good arrangement, trying to do both with the same method leads to a design that is poor for both cases.
Does any of that sound similar to your understanding of the situation? 8-)
|
|||||||||||||