Looking at the code, it looks like it is using JSON to serialize the object, via CFJSON. But I don't see how that's going to work with CFCs, since the serializer will see it as a structure, and when it is deserialized later, you'll end up with a structre, not a CFC.
A further quick review of the code gives me some reservations about the locking strategies employed and the fact that the cache is based soley on a hardcoded timeout value rather than something like usage metrics. If you're interested in reviewing a pretty complex caching system, have a look at how Transfer is doing it. Even if you don't use Transfer, Mark's created some pretty robust cache machinery. On Wed, Feb 18, 2009 at 9:17 AM, Gerald Guido <gerald.gu...@gmail.com>wrote: > > I saw this on RIAForge today. It may do what you want. > > http://cfobjectcache.riaforge.org/ > > -- > Gerald Guido > http://www.myinternetisbroken.com > > > "To invent, you need a good imagination and a pile of junk." > -- Thomas A. Edison > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:319483 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
