Hitachi-ZYWRLE Encoding Number (was RE: Introduction of New
VNCcodec)
Hitachi Systems & Services, Ltd.
micro-vnc "at" ias.hitachi-system.co.jp
Mon Feb 5 03:05:00 2007
Hi Wez,
<005001c746c5$f912f7e0$0202fea9 "at" sturton.local> $B$N!"(B
"Hitachi-ZYWRLE Encoding Number (was RE: Introduction of New VNCcodec)" $B$K$*$$$F!"(B
""James Weatherall" <jnw "at" realvnc.com>"$B$5$s$O=q$-$^$7$?!'(B
>I've had encoding number 17 allocated to Hitachi ZYWRLE - using this
>encoding number will ensure compatibility with standard VNC and
>VNC-compatible releases. The next release of the VNC codebase will
>therefore include an encoding "place-holder":
>
> const int encoding3rdPartyHitachiZYWRLE = 17;
Thank you for your allocating!
BTW, some people tell me that 17 has already been used by other
people and we should change this number. Its name is "krfb"
though I don't know about detail of it.
Do you know about it? Do you think that we should change this number?
>Not necessarily - which particular VNC version, or VNC-based software, you'd
>like to patch your encoding against is entirely up to you. I'd would
>recommend either patching against the standard VNC release, or a
>VNC-compatible project such as TightVNC.
OK, I understood.
I think that the patch for RealVNC 4.x is meaningful and porting
isn't difficult. So, I try it:
* In rfb project,
* Copy ZRLEEncoder.[cxx|h]/ZRLEDecoder.[cxx|h] to
ZYWRLEEncoder.[cxx|h]/ZYWRLEDecoder.[cxx|h] and modify it.
* register them in Encoder.cxx/Decoder.cxx.
* Modify zrleEncode.h/zrleDecode.h for ZYWRLE. The modification
is only functionable when include from ZYWRLEEncoder.cxx/
ZYWRLEDecoder.cxx.
* Add our zywrletemplate.c.
* Modify a bit of viewer for selecting our encoding.
Regards,
---
Noriaki Yamazaki
Administrator of micro-VNC
Research & Developement center
Hitachi Systems & Services, Ltd.