apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: [doc patch] clarify the issue with uniqueness of the key in apr_pool_userdata_set
Date Thu, 25 Sep 2003 07:35:20 GMT
Cliff Woolley wrote:
> On Thu, 25 Sep 2003, Stas Bekman wrote:
> 
> 
>>Hopefully this makes things less confusing.
> 
> 
>>   *      use for their data.  It is possible to accidentally overwrite
>>   *      data by choosing a key that another part of the program is using
>>   *      It is advised that steps are taken to ensure that a unique
>>- *      key is used at all times.
>>+ *      key is used at all times. This is of course inside one pool;
>>+ *      Two pools, or a pool and sub-pool can use identical keys.
> 
> 
> Getting better... how about:
> 
> "... It is advised that steps are taken to ensure that unique keys are
> used for all of the userdata objects in a given pool at all times.
> Careful namespace prefixing of key names typically helps to ensure this
> uniqueness."

+1

Though I'd double overstress that one doesn't have to ensure uniqueness across 
two pools, and even a pool and its sub-pool.


__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


Mime
View raw message