Re: [Phpwiki-talk] Automatic config rewriter php -> ini

[Dan F. <dfr...@cs...>]

One disadvantage: you'll always support two ways (ini and php). This 
requires more code maintenance. I claim you'd be happier if you could 
somehow easily migrate people, so in the end you only support one way. 
For example, offer a tool that takes an index.php and makes an INI file 
out of it. Then this tool can be deprecated and go away after a few 
releases.

In general, supporting fewer ways to do the same thing in the long run 
is good.

Just an idea.

Dan

Joby Walker wrote:

> Matthew Palmer wrote:
>
>> Has anyone made any progress in this area?  The major hold-up for me
>> updating Debian to 1.3.1[01] is that it'll force every PHPWiki user in
>> Debian to rewrite their config files, which is unlikely to make them 
>> jump
>> for joy.
>
>
> I'm a good way toward being done.  Been busy with work, getting a new 
> laptop, and rebuilding my windows server at home.  Once I have the CLI 
> client working and tested I'll commit it.
>
>>
>> I did have one (potential) brain-wave, which would also, as a 
>> side-effect,
>> solve the major cause of complaint against the ini-file system.  Put
>> together code which parses the INI file and writes a config.php full of
>> define()s and whatever else takes your fancy, and source *that* 
>> instead of
>> doing an INI parse every invocation.  Then, just have a bit of code that
>> compares the mtime of config.ini with that of config.php, and rewrite
>> config.php if it's older than config.ini.  The first user to hit the new
>> config file gets a 1-2 second slowdown, maybe, but that can be server 
>> lag,
>> and everyone else gets smokingly fast response times.
>>
>
> Yeah thought of that too.  It'll be an option for the CLI client to 
> build a config.php.  Then if config.php is present it'll use it 
> instead of config.ini.
>
> jbw
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk