Ray,
I also forgot to say that the cacheing tags register all cached objects
that they contain, so that if you update an object in the codb you can
flush all cached data containing that object. This was the original reason
for creating the tags. The users and groups just seemed like a logical
thing that I wanted to have.
They also support caching the generated HTML to a database which is handy
for clustered servers.
Spike
At 15:35 11/04/2001 Wednesday, you wrote:
>Spike, to handle users, why not simply use dynamic names?
>
><CFA_GeneratedContentCache ... CacheName="PageFoo_#Username#">
>...
></CFA_..>
>
>This would create a cached copy unique for the user.
>
>I've done simular things for a page that had 3 'modes' depending on the url
>param.
>
>=======================================================================
>Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
>
>Email : [EMAIL PROTECTED]
>ICQ UIN : 3679482
>
>"My ally is the Force, and a powerful ally it is." - Yoda
>
> > -----Original Message-----
> > From: Spike [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, April 11, 2001 9:23 AM
> > To: Spectra-Talk
> > Subject: RE: Page Templates vs. Objects
> >
> >
> > I love it too, but I found that it didn't have anywhere like enough
> > flexibility for dealing with sites that have different content for
> > different users.
> >
> > I ended up writing one myself that handles group and user level
> > caching for
> > a particular block of content. Also nested tags intelligently handle the
> > cache timeout.
> >
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
