One tip that might help if you go down the route of caching it all and then
the need arises to cut back on the cached data, abstract out the call to get
data so caching or not caching has no effect on the output of data.
For example, don't use
<cfquery name="APPLICATION.yourQuery">
</cfquery>
APPLCIATION.yourQuery.yourColumn
But instead maybe use this
<cffunction name="getQuery">
<cfset var q>
<cfif cache conditions here>
<cfquery name="APPLICATION.q">
</cfquery>
</cfif>
<cfreturn APPLICATION.q>
</cffunction>
<cfset localQuery = getQuery()>
#localQuery .yourColumn#
Does that make sense? Anyone care to comment? Logic might be wrong but I'm
just trying to explain the concept.
Ade
-----Original Message-----
From: Damien McKenna [mailto:[EMAIL PROTECTED]
Sent: 23 February 2005 22:36
To: CF-Talk
Subject: RE: Reason to *not* store lots of data in Application scope?
> -----Original Message-----
> From: Adrian Lynch [mailto:[EMAIL PROTECTED]
>
> Maybe only cache current data? If it's less likely someone will look
at last
> years entries, exclude them from the cached data. It'll be easiest to
wack
> it all in there and see how it works out, if you think it might be a
problem
> then look at ways of trimming the amount you cache.
That's an idea.
The way it'll work is you'll have a master page that lists a variety of
different events, each with different dates, occurrences (some are
once-off, some are weekly, etc). In addition there'll be two miniature
calendars on the side of the page with color-coding to state what sort
of events are on that day. Visitors will be able to click on an event
title to see the detail (article text) and a list of similar events.
There will be an archives page for each event type, which will list all
past events that are not on the main page. Lastly, there will be a
large calendar view (clickable from the mini calendars on the master
page) which will display the events for an entire month along with links
to the detail page for each one.
>From that I was going to cache the processed calendar information and
leave the event text in the database. Simply storing that amount of
information shouldn't be too much of a burden IMHO.
On a related note, I was add icalendar support but when Outlook doesn't
support icalendar files properly there's no point.
--
Damien McKenna - Web Developer - [EMAIL PROTECTED]
The Limu Company - http://www.thelimucompany.com/ - 407-804-1014
#include <stdjoke.h>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196223
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
