Hmmmmm there is another way. If the server has access to the Internet, you could store all the variables on a server of your choice and use a webservice, HTTP GET or CFFTP etc etc to grab the XML file or what have you from the server you control. Read in the values etc. This could double as a registration/activation phase also.
:) Aaron ----- Original Message ----- From: "barry.b" <[EMAIL PROTECTED]> To: "CFAussie Mailing List" <[EMAIL PROTECTED]> Sent: Monday, May 24, 2004 5:37 PM Subject: [cfaussie] RE: looking for ideas - storing config settings > >> Are you amenable to storing the values in a database table? > > sadly, the db schema is now locked in stone with no changes to be made > (lots of reasons, a long story) > > It's probably a really good idea - the creation of the DSN is one very few > constants of the whole distribution process (apart from what Taco pointed > out - each applications directory name, although each app could go > _anywhere_, not even in the same parent folder...) > > mapping IIS virtual dirs will also need to be considered. One of the first > things to get running is Flash Remoting. > > a right royal can 'o' worms, here. > > barry.b > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > > MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia > http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
