<< If you run the query directly into session.cache_query rather than using the intermediate q, you could do exactly what you asked. For Google and other bots/users who don't keep sessions, your check to see if session.cache_query would always show it's nonexistant, so it would always be rerun. >>
Gotcha, I see what you mean. <cfquery name="session.cache_query" datasource=".."> Sounds like a good approach. The only potential downside is the overhead required to store and then later delete the cached queries for clients like Google/yahoo/msn/etc bot sessions. Between these guys and clients with no cookies, thousands of unused sessions an hour are created, which means that for sessiontimeout minutes that cache_query memory will be wasted. Could always manually delete the variable based on user_agent I suppose. Have never stored queries directly into session scope, but would be interested to hear if anyone has any experience with performance of such under load vs using local variables. >If you run the query directly into session.cache_query rather than using >the intermediate q, you could do exactly what you asked. For Google and >other bots/users who don't keep sessions, your check to see if >session.cache_query would always show it's nonexistant, so it would >always be rerun. > >--Ben > >Terry Ford wrote: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228489 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
