coldfusionJedi

<cfset sleep(9000)>
Done sleeping.

<cf_scopecache scope="application" name="mycodeisntslow" timeout="3600">
<cfset sleep(9000)>
Done sleeping.
</cf_scopecache>

This entry was posted on Thursday, February 28, 2008 at 8:01 AM. It was filed in the following categories: ColdFusion. It has been viewed 1,594 times and has 13 comments.

TweetBacks

Comments

[Add Comment] [Subscribe to Comments]

• Comment 1 written by John C. Bland II on 28 February 2008, at 10:28 AM

  

  Can I put the cache in the application scope but in my cache struct inside of that scope?
  
  ie - application.cache.mycodeisntslow vs application.mycodeisntslow
  
  Thanks.

• Comment 2 written by Raymond Camden on 28 February 2008, at 10:31 AM

  

  John, I read your question twice - and I still don't get it. What are you asking?

• Comment 3 written by Aaron Lynch on 28 February 2008, at 4:16 PM

  

  I think he is asking if he can store the cached data in a struct of his own choosing.
  
  In other words, instead of just scope="Application", there could be an optional attribute of structName...
  
  
  scope="Application" structName="cache"
  
  
  That is my take on it at least.

• Comment 4 written by Raymond Camden on 28 February 2008, at 5:28 PM

  

  Well, if so, the answer is no. ;) You can't dictate _where_ in the scope stuff is cached.

• Comment 5 written by Charlie Arehart on 1 March 2008, at 2:21 AM

  

  Thanks for posting it, Ray. I've now updated my pointer to it (along with many other CF-based caching solutions--and several dozen other CF tools) at:
  
  http://www.carehart.org/resourcelists/tools_to_con...

• Comment 6 written by Nate on 22 May 2008, at 5:56 PM

  

  I just learned about this custom tag today and it's really helped me out in a big way. Many thanks for this great work of yours. I've got a question. When would you want to use this with the request scope. I can understand how this is used in the application of server scope, but I can't imagine how it's useful in the request scope.

• Comment 7 written by Raymond Camden on 22 May 2008, at 7:55 PM

  

  I honestly can't think of a great reason to use the Request scope for the cache, but since it was so easy to add support, I figured what the hey.

• Comment 8 written by Nate on 2 June 2008, at 11:42 AM

  

  Can you think of a reason why some code fragments inside a cf_scopecache tag might randomly get repeated when first cached? Clearing the cache seems to correct this problem most of the time.

• Comment 9 written by Raymond Camden on 2 June 2008, at 1:51 PM

  

  Yes, I can think of a way. Maybe the tag gets confused and both caches and lets the original output through.
  
  I don't see this here, but if you can try to make a reproducible case, I'd definitely appreciate it.

• Comment 10 written by Nate on 3 June 2008, at 4:49 PM

  

  It turns out that my problem had absolutely nothing to do with Scopecache. It was a problem in a SQL query and I was simply confused because I made that change at the same time that I added your Scopecache.
  
  
  I have a new question for you / feature request.
  Let's say Scopecache caches 10000 code fragments and the memory/size of those variables starts taking up too much RAM. Might it be a nice feature to automically clear 2000 or so variables(those variables with the smallest hit count) when that happens?

• Comment 11 written by Raymond Camden on 4 June 2008, at 8:39 AM

  

  Yeah, that would be nice. I'd like to have a optimize type action that takes a 'strength' (ie, how much to clean) and the tag will clear out based on hitcount/last used type values.

• Comment 12 written by Nate on 8 August 2008, at 12:50 PM

  

  Here's another feature request if you ever find the time for it...
  
  How about a way to save the cache and restore it at a later time after a server is shutdown and restarted? Keeping a history of the cache on a daily or weekly basis would be a very nice feature.

• Comment 13 written by Raymond Camden on 8 August 2008, at 3:00 PM

  

  Ah, so basically, cache to the file system. In theory, you could do expires="never" then.
  
  Log a bug request for this at RIAForge. (If I didn't turn it on, bribe me with a beer and I'll do so.)

[Add Comment] [Subscribe to Comments]