Re: PHP web farms (i.e. why msession or something like it)

Daniel Lorch wrote:

I'd like to make a suggestion here: What do you think of splitting up the current PHP Manual into three major parts: 1. Developing in PHP ("for PHP users") 2. Extending PHP 3. PHP for System Administrators Part 3 would cover all topics interesting only to a system administrator, such as installing PHP, security issues (open_basedir, safe_mode, alternatives such as fastcgi, tweaking the configuration on a vhost basis, ..), installing PHP on web farms etc.. These topics usually don't interest the average PHP developer - why keep it in the same manual, then? What do you think about this? +1 - Maybe even consider adding to part 2 some documentation on developing PHP itself. Right now, one must read the few files on the Zend API, some coding standards, subscribe to this list, and use the force (read the source) - not that this approach is all bad.