Jyri
 thanks a ton for looking into this.

Jyri Virkki wrote:
> Sriram Natarajan wrote:
>   
>> PHP5 Feature Enhancements
>>     
>
>   
>> This case seeks Micro/Patch Release Binding.
>>     
>
> Is this same as all previous PHP cases?
>
>
>   
yes
> You'll want to state "This project depends on APR case 2009/XYZ and
> cannot deliver before it" (XYZ being the APR case Jeff is floating, no
> number available yet).
>
>   
Ok, Will do.
>
>   
>> 2.1 Provide PHP extension specific statistics
>>
>> Provide the ability to deliver statistics of 3rd party extensions like APC
>> and memcache usage statistics by delivering a separate SUNWphp52r-stats 
>> package.
>>     
>
> To continue discussion from previous thread, the case needs more
> supporting info for this particular delivery choice.
>
> The case seems to carve out the home SUNWphp52r-stats for
> stats-reporting php files. It's not yet clear to me why a user must
> want either all of them or none of them (consider not just the two
> delivered here, but all potential future ones which would then
> naturally fall into this -stats bucket).
>
> OTOH, earlier you mentioned these are effectively just samples, user
> must enable their use. Ok in that case, why SUNWphp52r-stats, instead
> of just delivering them in SUNWphp52u? The corresponding extensions
> themselves are all in SUNWphp52u already.
>
> This division where -stats are optional but only at the granularity of
> getting either none or all seems unintuitive to me given the info in
> the case so far.
>
>   
Ok.

We will deliver the same php statistics scripts within SUNWphp52u and 
the glue configuration file for apache within apache sample 
configurations directory. 

>> 2.2 Provide sample script(s) to help configure PHP runtime with other 
>> web server(s)
>>
>> Deliver a sample script within current PHP package to help configure PHP 
>> runtime
>> with other web server(s) like Sun Java System Web Server.
>>
>> These scripts will be delivered within SUNWphp52u package under
>>
>>                /usr/php/5.2/samples/scripts
>>     
>
> The exported table lists only setup-sun-webserver.sh. Does this case
> establish the above dir as a location for all such future scripts?
>   
yes. Does that make sense ?
> What does a customer do with setup-sun-webserver.sh? Run it and hope
> for the best? ;-) The case doesn't really explain. Does the script
> depend on anything from WS7?  Provide any options?
>
>   
Ok, Will explain it

>> 2.4 Provide additional DTrace probes within PHP runtime
>>
>> Deliver additional DTrace probes within PHP runtime by providing patches to
>> Zend engine. These additional patches will be contributed to the 
>> upstream community.
>>     
>
> Provide some background on how are these different from currently
> included dtrace extension.
>
>   
These probes provide more insight on what is happening within Zend core 
. Current PHP DTrace probes only provide insight as to when a function 
is called . Ok, Will add this information within the ARC case.
>   
>> 3. Interfaces:
>>     
>
> This section needs restructuring work. It has two sections "3.2" and three
> sections with imported interfaces (3.1, 3.2, 3.3).
>
> Refactor it to end up with only two subsections:
>
>   3.1 Imported Interfaces
>    [... document changes to imported interfaces ...]
>
>   3.2 Exported Interfaces
>    [... document changes to exported interfaces ...]
>
>
>
>   
>>        OpenLDAP                     External/Volatile  PSARC/2008/507
>>     
>
> As mentioned in more length in APR comments, 2008/507 doesn't export
> anything as External so above line cannot be correct.
>
>   
>>        Apache with OpenLDAP         External/Volatile  
>>     
>
> Does this case make PHP use some new APIs from Apache? What precisely
> is the above line importing? Provide some detail.
>
>   
No, it does not use any new API's. All it does is to simply link with 
OpenLDAP. So, do I need provide any specific information in that case ?

Reply via email to