Hi, Jyri Virkki wrote: > I went through all the Apache threads so far this afternoon to > summarize the current state of discussion, here is where I believe > things stand: > > - The next case will support both worker and prefork MPM. I believe > we have closure on this. Seema has posted details on the delivery. > > - Configuration of MPM choice. Seema, can you summarize the answer? > > - Closure on file layout versioning. The 2007/169 case had > /usr/apache2 (and corresponding places in /etc and /var). There's > been much discussion on whether to stay the course or permit minor > releases of 2.x to coexist (and there are several way to accomplish > that, but the higher order question is whether coexistence is the goal). > The main argument for this appears to be for upgrades, so that upgrading > from S10 doesn't break a working installation. >
not sure if it is part of file layout area or not, but I noticed a few things we could add automatically on disk to ease the developer experience (based on the coolstack content): 1/ a favicon.gif file in htdocs of apache to avoid useless entries of 404 or file not found in the logs. OpenSolaris logo? 2/ a better index.html (and maybe more files for samples) to describes 'what' works when 'it works'. 3/ a description of the smf apache service in services. 4/ for the 'user' created via sxde installation process (build 70), other than root, rbac settings to operate apache 5/ for this 'user' (I call him Mister D, the D in sxDe), a default public_html directory in in home directory with good initial content. I am in the middle of writing a document regarding what this Mister D will need (sxde installation changes, visual panels changes, user/group default definitions changes, user privileges changes, etc...), but this is what I remember for the apache area. Also, I've seen a few threads regarding the web-stack 'optimal' performance and flag settings, but I thing we need to discuss how we set these flags and options with 2 point of views: 1/ the Developer (our SAMP target I think): - no real need for added performance tuning - for example, saving a php file, and page reload on the browser must work without restarting apache:) - log managment (on, of, rotation, view,...) 2/ the Deployer of an AMP app - management flags - optimal Solaris performance. How do we balance these 2 conflicting roles in SXDE? Comments welcome, Thanks, Ludo > - There was discussion of adding a 'build' directory. Closure? > > - There were various proposals on directory name changes (modules, > conf.d) but the consensus was that names should not change unless > there is a strong reason. So I believe there is closure on existing > names (libexec, extras). > > > Thoughts? Corrections? Etc? Hit list reply... > > >
