Okay,
I've been working on the draft in my hotel room (not much else to do),
and I want to make the following simplifications:
Only two encodings:
. Hextile with optional zlib compression
. Tight-1.2.x encoding (I'm using 1.2.4 as my guide)
I'd like to drop the "text" encoding as Eric Hill pointed out that in
many circumstances, the cache encoding I've proposed will be even more
efficient than a text encoding. So I will talk to Constantin about the
possibilities of adding the cache tile encoder to the Tight encoding.
The reasons for dropping older encoders is to help small footprint
platforms. Remember, in RFB 4.x nearly everything is optional, so it is
possible to make a very small server and viewer.
Only one bi-directional transfer mechanism. This will have extensions to
cope with files and printing, but essentially, it's a "bag o' bits"
approach. I don't want the protocol to get too tied up with
platform-specific intricacies.
Andrew
|
