> Fabian,
>
> Here is the svnprops I have in my config: I looked through the frontend_file
> class and did not see what you were referring to:
>
> Zend http://framework.zend.com/svn/framework/standard/trunk/library/Zend/
>
> I also rummaged through the lab and incubator directories. Can you assist
> with the location?
>
/**
* Change the master_file option
*
* @param string $masterFile the complete path and name of the master file
*/
public function setMasterFile($masterFile)
Or you can use it throw the setOption method.
/**
* Public frontend to set an option
*
* Just a wrapper to get a specific behaviour for master_file
*
* @param string $name Name of the option
* @param mixed $value Value of the option
* @throws Zend_Cache_Exception
* @return void
*/
public function setOption($name, $value)
Regards
> Thanks again.
>
>
> Fabien MARTY wrote:
>
>> Hi,
>>
>> jkush1121 a écrit :
>>
>>> The more I think about this, the more I believe that by setting a new
>>> master_file, I'm simply removing the monitoring service on that caching
>>> object, so I probably would need to make separate cached instances. This
>>> could be beneficial, however, in providing more control on each xml
>>> configuration. Do you believe, if what I am saying is true, that the
>>> frontend_file is extendable to manage multiple instances? I don't see why
>>> it
>>> couldn't...
>>>
>>> Thanks for the help!
>>>
>>>
>> There is an open issue for multiple dependencies in
>> Zend_Cache_Frontend_File :
>>
>> http://framework.zend.com/issues/browse/ZF-4247
>>
>> I don't know if it can help you but there is a method in SVN trunk in
>> Zend_Cache_Frontend_File to be able to change the "master_file" without
>> making a new object.
>>
>> Regards
>>
>> Fabien
>>
>>
>>
>
>
没有评论:
发表评论