which is using a factory loader for it's object instantiation. The
interesting factor, however, is the usage of Zend_Cache_Frontend_File. After
doing some research, I realized that this solution would benefit my scenario
alot more than my current solution. However, the Frontend_File Cache speaks
nothing in regards to having multiple files to manage.
(
http://code.google.com/p/zfe/source/browse/framework/trunk/library/Zfe/Config.php
)
Here's my current solution:
1.) Is Cache Available for configuration && Is Core Configuration Allowing
to use this cache?
Yes -> Use Cache; No -> Continue
2.) Begin parsing/merging of various XML configuration files, DB
Configuration Mergings, and so on.
3.) Save cached end result for usage with the next load. Apply core
configuration settings neccessary.
I have a separate core configuration which I am using to manage the caching
logic, but the frontend_file aspect would be alot nicer. My concern is,
however, having to create several frontend_file caching instances to
maintain the separate master_files.
Is it possible, instead, to just reassign the master_file on each XML
configuration load via setOption()? To better word the question, can a
single Zend_Cache_Frontend_File instance manage multiple master_files? Is it
even worth it in the end? I am hesitant because it seems I'd have to end up
just running a large loop of merging cached configuration data objects,
versus my current solution of using one single object. On the other hand, my
configuration manager is not effective as it requires me to make an extra
check with every cache load/save attempt.
-jk
--
View this message in context: http://www.nabble.com/Zend_Cache_Frontend_File-monitoring-multiple-XML-master_files---tp20414052p20414052.html
Sent from the Zend Core mailing list archive at Nabble.com.
没有评论:
发表评论