Re: 1 cset was pushed to core/stable: make persistent database connections con...

Marcel van der Boom wrote:
> On the one hand you comment out the shutdown handlers to shape things up 
> for 1.0 and on the other you introduce a new item in config.system.php 
> with mods to xarCore and xarDB for new functionality.
> 
> Which of the two modus operandi is it?  We ( I ) give people a hard time 
> for changes of lesser impact than this one.
> 
> marcel
> 
Both changes came for the same reason, namely core tweaks you would
routinely do at each installation/upgrade to improve performance for
big sites (= dedicated servers or multiple servers).

Typical examples are the linux.com and sourceforge.net sites, but
other large sites would benefit from this as well. I've had the
persistence option in mind for years, but it's only when I saw how
big a difference it can make for those sites that I felt it was
appropriate to make this configurable, rather than forcing "non-
-developers" to tweak the core each time they want to upgrade.

So yes, this too is to shape things up for 1.0 - making Xaraya
fit to run in production by default, rather than having it
configured with all the bells & whistles for debugging. :-)

[As I see it, if you're a developer and you're playing with
shutdown functions in the core anyway, you might as well uncomment
an extra line - but if you're a sysadmin trying to run a big site,
I'm sure you'd prefer to change a line in config.system.php once,
rather than hacking the core again after each upgrade.]


Of course, if you're really opposed to this, feel free to remove
again - but I feel we need to start thinking beyond the "early
adopter" crowd (and ourselves), who aren't afraid of diving into
the core and tweaking things to their liking...

No doubt you also have a few tricks up your sleeve to improve
things in production - now would be a good time to think about
whether those should become configurable too (depending on the
impact for normal/tuned operation etc.). Don't you think so ?

Mike.