> I agree that CFCs, as a general rule, should not directly > output > content. I use CFCs for my backend logic and data > processing. That > said, I do use CFCs occasionally to generate content > usually within a > <cfsavecontent> tag. I use this approach to 'cache' > content that > changes infrequently and store the content in a database > prior to > returning the content. I use the cfc to check the > existence of the > cached content in the database and return the cached > content if it has > not expired. If the content does not exist or has > expired, I then > re-generate the content, store it, then return it. I find > CFCs are > extremely useful in situations like this.
I've used custom tags to do this for years. heh. :-) > I was hoping to hear that CFMX 6.1 would allow > instantiated objects in > the client scope. How useful would that be? I know you > can use them in > the session scope, but session scopes run the risk of > colliding with > other session if you forget to use <cflock>. I've heard > that with CFMX > you no longer need to lock session scopes. This is true. You don't have to worry about colliding sessions in MX, so you're good there and I suspect what you hoped to accomplish with client scope will be fine in the session. The client scope is still rather limited by its reliance on a database or cookies or the registry any of which is liable to cause performance issues if not in the case of the registry serious issues in general on the windows server if/when the registry fills up later. s. isaac dealey 972-490-6624 team macromedia volunteer http://www.macromedia.com/go/team chief architect, tapestry cms http://products.turnkey.to onTap is open source http://www.turnkey.to/ontap ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To unsubscribe: Send UNSUBSCRIBE to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org
