Any thoughts about moving the config file to a subdirectory off our web site for future versions instead of the web root? I'm imagining a future where we have to keep tons of these around for backwards compatibility which makes things a bit messier...
-Nick On Mon, May 27, 2013 at 2:14 AM, OmPrakash Muppirala <bigosma...@gmail.com>wrote: > On Sun, May 26, 2013 at 11:01 PM, Justin Mclean <jus...@classsoftware.com > >wrote: > > > Hi, > > > > > I think we should create a config 3.0 with these changes. Whenever > there > > > are structural changes to the config xml, we do that in a new version. > > > > There's no real major structural changes just more data - it's backward > > compatible with the old version - but no complaints if you want to make > 3.0. > > > > Thanks, > > Justin > > > I am thinking of scenario where the older version of the 2.0 config is > cached by the AIR runtime. That would be a pretty hard for end users to > fix. > > I will go ahead and make this change. > > Thanks, > Om >
