> >The answer is pretty much "never". The other encodings (RRE and CoRRE)
are
> >really there to support older clients and servers, and also to make it
> >trivial to write new ones, since Hextile is relatively complex by
> >comparison. The RFB Clock mentioned on the VNC site, for example, uses
RRE
> >to render itself.
> >
> >The only other encoding you might use is Raw, in conjunction with
CopyRect,
> >if your network is a high-bandwidth one, in which case you save by not
> >encoding the data.
>
> I beg to differ - RRE and CoRRE are in fact *more* bandwidth-efficient
than
> Hextile for the case of large flat areas of colour. The reason for this
is
I'd assumed the original post was querying which encoding to select as the
main encoding from a viewer, not which encoding is best for any particular
special case. Hextile is best overall because of the standard encodings it
gives the best average compression. It does so because it performs almost
exactly the algorithm you describe, to discover when to use Hextile-RRE and
when to use Raw encoding. It will use significantly fewer CPU cycles than
the algorithm you describe, however, thus giving better latency.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
