Hitachi-ZYWRLE Encoding Number (was RE: Introduction of New VNC codec)

[James Weatherall]

Hi Steve,

As I pointed out in my original response, the problem with them having
patched against the UltraVNC hobby project is that that's not
VNC-compatible.  Better to product patches against something VNC-compatible,
or, better still, the standard VNC codebase, if you want people to be able
to use it!

Cheers,

Wez @ RealVNC Ltd.
 

> -----Original Message-----
> From: Steve Bostedor [mailto:sbostedor "at" vncscan.com] 
> Sent: 02 February 2007 17:29
> To: 'James Weatherall'; 'Hitachi Systems & Services, Ltd.'; 
> vnc-list "at" realvnc.com
> Subject: RE: Hitachi-ZYWRLE Encoding Number (was RE: 
> Introduction of New VNC codec)
> 
> Why not patch against both?  The UltraVNC and TightVNC 
> flavors are just as
> popular as RealVNC.  Why limit yourself to just one version of VNC?
> 
> 
> Steve Bostedor
> Bozteck Solutions
> http://www.bozteck.com
>  
>   ------------------------------------------------------------------
>    Take control of your network with
>    VNCScan Enterprise Network Manager
>    Download: http://www.vncscan.com
>   ------------------------------------------------------------------
>  
> 
> 
> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com 
> [mailto:vnc-list-admin "at" realvnc.com] On
> Behalf Of James Weatherall
> Sent: Friday, February 02, 2007 7:31 AM
> To: 'Hitachi Systems & Services, Ltd.'; vnc-list "at" realvnc.com
> Subject: Hitachi-ZYWRLE Encoding Number (was RE: Introduction 
> of New VNC
> codec)
> 
> Hi Noriaki-san,
> 
> 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;
> 
> > >I note that you have a version of the UltraVNC hobby project 
> > patched with
> > >your scheme.  Since the UltraVNC project is not 
> > VNC-compatible, you will
> > >need to switch to a VNC-compatible codebase if you want to 
> > provides VNC
> > >viewers & servers with your custom encoding.
> > 
> > You say that I need to make patch for RealVNC server, don't you?
> > (Sorry to my poor understanding to English...)
> 
> 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.
> 
> Regards,
> 
> --
> Dr James Weatherall
> Chief Engineering Officer - http://www.realvnc.com - RealVNC Ltd
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list