I'm not sure what's so magical about using the Registry. Everyone hates using the registry because it is platform-specific and requires more coding to do than just grabbing the settings from a file in the current directory.
It's much easier to do cross-platform code if you keep away from using the already bloated Windows registry to store your data. UltraVNC is a Windows-only flavor of VNC but the VNC code base is meant to run on all platforms. It makes little sense to stick things in the Registry and require the extra coding for each platform. - Steve Bostedor -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Long, Phillip GOSS Sent: Thursday, May 17, 2007 1:23 PM To: vnc-list@realvnc.com Subject: RE: VNCSCAN: UltraVNC with Vista Support Yury Averkiev wrote: > Also worth mentioning that they made a very controversial decision to > starting using an .ini file instead of windows registry, which in my > opinion was not very bright idea. I really hope RealVNC won't choose > this path. And the UltraVNC's new special Vista helper service is a > proprietary one, so there is nothing much Real/TightVNC people could > look at. > > Kindest regards, > Yury Averkiev > SmartCode Solutions - Network Management Without Barriers > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Steve Bostedor > > Sent: Thursday, 17 May, 2007 9:11 PM > > To: vnc-list@realvnc.com > > Subject: VNCSCAN: UltraVNC with Vista Support > > > > The UltraVNC team has been working on a release of their VNC client/server > > for Windows Vista and have finally released their first beta. As far as I > > can tell, they are the first free flavor of VNC to release something that > > works in Vista as a service. > > > > The forum thread for this beta release is here: http://tinyurl.com/24kuv5 > > > > Hopefully, the authors of RealVNC and TightVNC can look at their progress > > and get something similar done with their open source versions of VNC. > > > > Thank you, > > > > Steve Bostedor > > http://www.vncscan.com > > VNC Management Made Simple Using a .ini file is not a _standard_ way to set preferences in Windows, but by decoupling the application from the Registry, it is less likely to fall prey to an inadvertent Registry change (and we all know that That Never Happens, right?). My gut feeling is that if the Registry is currently being used, it should continue to be used (fewer coding changes), but any new code is, IMHO, better released without using the Registry. -------------------------------------------------------- Goss ... Innovation for Business NOTICE: This e-mail and any attachment(s) may contain confidential and proprietary information of Goss International Corporation and/or its subsidiaries and may be legally privileged. This e-mail is intended solely for the addressee. If you are not the addressee, dissemination, copying or other use of this e-mail or any of its content is strictly prohibited and may be unlawful. If you are not the intended recipient please inform the sender immediately and destroy the e-mail and any copies. All liability for viruses is excluded to the fullest extent permitted by law. Any views expressed in this message are those of the individual sender. No contract may be construed by this e-mail. _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list __________ NOD32 2274 (20070517) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
