Re: [Philadelphia-pm] Persistent data directory

["Ken Fox" <kenfox@starlinx.com>]

FWIW if it's configuration data then by convention on win platforms it
should go in the registry since that was created to get rid of the myriad of
INI and config files.  Granted there's bloat associated with the modules and
such needed to access the registry. I would think that putting the location
of the config information file in a registry entry and then storing the data
in a more perlish way/location might make a tolerable hybrid solution. 

.... ken

-----Original Message-----
From: philadelphia-pm-bounces+kenfox=starlinx.com@pm.org
[mailto:philadelphia-pm-bounces+kenfox=starlinx.com@pm.org] On Behalf Of
Chris Nehren
Sent: Wednesday, November 16, 2011 11:29 PM
To: Nate Smith
Cc: philadelphia-pm@pm.org
Subject: Re: [Philadelphia-pm] Persistent data directory

On Nov 16, 2011, at 13:34, Nate Smith wrote:

> 
> How much data are you talking about?  If it's reasonably small, and 
> you are definitely only working with Win32, you could always consider 
> keeping it in the registry.
> 


What benefit does keeping it in the registry gain? Keeping things there
makes it more difficult to get them out later (have to use specialized
tooling); one has to consider where to store it (the registry is not really
the simplest datastore); one has to consider possible loss of data in the
event of a corrupted registry; and I can't see any real benefit.

--
Thanks and best regards,
Chris Nehren

_______________________________________________
Philadelphia-pm mailing list
Philadelphia-pm@pm.org
http://mail.pm.org/mailman/listinfo/philadelphia-pm


_______________________________________________
Philadelphia-pm mailing list
Philadelphia-pm@pm.org
http://mail.pm.org/mailman/listinfo/philadelphia-pm