folder is an implementation detail that you needn't worry about for setting
up your cache. It's purely an inside-the-framework thing and only serves to
speed up the framework. I can't think of a good reason to do anything but
ignore it unless you're debugging the core files.
I've deployed a couple FB4 apps, and it's great. The performance
improvements are the nicest thing in production, of course, since by that
time the app is just a black box. You can pretty much subtract the entire
execution time of the FB3 core file from each request. For simpler apps,
that can show a huge percentage improvement, and for apps that do a lot of
recursive calls to the fusebox, the savings is even greater.
-----Original Message-----
From: Nikhil Madani [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 11:27 AM
To: CF-Talk
Subject: Fusebox 4 and Caching
We have an existing application in FB3 that I'm planning to migrate to FB4
in the MVC pattern. Everything about FB4 with the MVC pattern sounds great
(I come from the Java world, so CFMX with FB4 and MVC seems a welcome
improvement from earlier versions)- my problem is this:
Our site/application's is configured to dynamically display a particular
category of products only, depending on the url string parameter that the
user comes in with, (or the default that we set). (99% percent of our
traffic comes from links from our business affiliate sites). We presently
cache on the basis of the different categories available- otherwise its not
possible to serve a large number of customers without overloading our
network.
Now, my question is- while I understand that FB4 itself does in a way
cache at the fuseaction level (parsed folder), how can I make this work with
our caching mechanism, which is to have different folders under the webroot
for a cached version of the app. for each category of our products?
Also has anyone out there deployed anything in FB4 at the production
level? Any drawbacks/improvements observed?
Thanks
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
