Jyri Virkki wrote: > Sriram Natarajan wrote: > >> I wish to deliver couple of minor php enhancement within build 109 (if >> > > COB today is about the last hour to get new features into b109, so > this thread is really targeting b110. > > >> Summary : >> 1. Provide sample script so that customers can hook up with open web >> server or Sun Java System Web Server. >> > > The idea is good, but can you provide more detail? > Well, the sample script (say setup-php-with-webserver7.sh) . Users running this script will be able to configure PHP as FastCGI within Sun Web Server 7. > >> 2. We would like to be able to deliver statistics of 3rd party >> components like APC as well as memcache usage statistics. To make this >> happen, we will need to deliver a separate package - say >> SUNWphp52r-stats which will deliver the following files >> >> /var/php/5.2/stats >> /var/php/5.2/stats/apc.php >> /var/php/5.2/stats/memcache.php >> /etc/apache2/2.2/conf.d/phpstats.conf >> >> User after installing this package, will be able to look at the apc or >> memcache (if it is being used) by running >> http://localhost/phpstats/apc.php or >> http://localhost/phpstats/memcache.php . The default configuration will >> allow access only from localhost. >> > > The above arrangement means that anyone who wants apc stats must not > only also get memcache stats (or the other way around) but also gets > them both enabled by default from phpstats.conf. Is it expected nobody > will want just one set of stats without wanting the other? > > what we deliver is PHP scripts provided by these extensions. Running this script will produce output only if that particular extension is configured and being used. For example, user running http://localhost/phpstats/memcache.php will not produce any output if user has not configured sessions to be stored with memcached.
> Are there any drawbacks to having all these stats pages (possibly > including future ones that may get added later?) in an all-or-none set? > > > The scripts (apc.php or memcache.php) which delivers these statistics are less than 10 Kb. So, I can't see size as the drawback in clubbing all these together. Also, customer can easily fine tune phpstats.conf to ensure that only apc stats are displayed and not memcache or other third party extension, I can't think of any drawback. Delivering each of these single script in a separate package delivers more maintenance headache than any thing else. >> 3. Provide additional DTrace Probes. (this is not yet included within >> the below 1 pager). I will let expert to chime on whether should adding >> additional DTrace probes within PHP be a separate 1 pager in itself or >> could this be plugged into here. >> > > Ok. I will try to get all of these into a single 1 pager.. > Depends on the timing but if you can align the work, I'd do one "PHP > Enhancements" case to cover all new PHP features being introduced this > month (possibly including the OpenLDAP use, which you didn't mention here). > > Very True. What is the deadline to make it into build 110 ? > >
