On Thu, Jan 21, 2010 at 2:34 AM, Dorioo <[email protected]> wrote: > Main benefit I was looking for is not having to manage the ehCache instance > myself.
You know the eHCache provider in Transfer manages this for you? You just call .shutdown() on transfer, and the ehCache Cache is shutdown properly. No more management than that necessary. > If I fail to properly shutdown an ehcache instance, it remains in memory. > Using the CF9 object cache, I simulate a "shutdown" by discarding all of the > objects in the CF9 object cache that begin with my providers naming prefix. > And if that were to fail for any reason, the objects themselves have a > timeout and would be purged in time anyway by CF9. > > Obvious limitations are with the limited ways in which CF9 allows you to > interact with its object cache but so far it's looking viable for my needs. > When you get it finished, feel free to post it to the list, and I can add it as a cache provider in Transfer. Mark -- E: [email protected] T: http://www.twitter.com/neurotic W: www.compoundtheory.com Hands-on ColdFusion ORM Training @ cf.Objective() 2010 www.ColdFusionOrmTraining.com/
-- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
