Hello,
Scenario/assumption/premise of how cached query works
with CFMX:
query ("getAllEmployees"), cached within 15 minutes
<cfquery name="getAllEmployees" datasource="someDS"
cachewithin="#CreateTimeSpan(0,0,15,0)#">
-- SELECT statement sql here
</cfquery>
User A requests this query at 7:34PM EST;
User A|C updates data that affects the above query
resultset at 7:40PM EST;
User A logouts at 7:41PM EST;
User B requests the same query at 7:44PM EST;
User D requests the same query at 7:46PM EST;
My understanding is CFMX would send all three same
query users (User A, B, D) with the same resultset
albeit concerning data has changed.
If this understanding is correct, I still must say,
CFMX is absolutely not at fault, A) the programmer has
determined that using 15 minutes cache would be of
more value in terms of application efficiency vs. data
currency; B) it seems that it makes absolutely no
sense of checking if relevant query data is still the
same before applying cached one, (if check, why use
cache? overhead...) But this is not what I'm getting
at.
What I'm speculating here is this:
If CFMX Disables all cached queries upon logout
in this case User A logs out, all his cached queries
expires, then,
User B and D would get current/accurate data.
Does it make sense to you? If so, how would one go
about expiring all associated queries upon a user's
logout, expires all sessions pertaining a particular
user is easy, ...
DL
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=9
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=9
Get the mailserver that powers this list at http://www.coolfusion.com
