In the testing I've done, if cflogin isn't executed every request, any request in which it doesn't execute will lose synchronization with the login information for the associated session. Even if the cflogin tag doesn't execute the code which it wraps, the fact that it checks to see if a user is logged in to the app and executes the code it contains if not is enough to keep it aware of the logged-in user.
If you have 3 successive requests, first executes CFLOGIN to log a user in, one in which cflogin doesnt' execute, and a third one in which it does execute, the third one won't resync with the first one. The second one breaks any association with the login data that was created by the first one... so the third one will reflect the fact that there's no logged-in user. CFLOGIN is pretty simply, but it has some ideosyncrasies... and the misunderstanding of them is part of what confuses people about it so much.
Anyway, just thought I'd toss that in next to your comment on application names being per-request to keep an association alive. CFapplication isn't the only place that this idea shows up.
Laterz,
J
On 5/14/05, Sean Corfield <[EMAIL PROTECTED]> wrote:
On 5/14/05, Mark Mandel <[EMAIL PROTECTED]> wrote:
> I still stand by namespaces - i.e. some form of either
> a) programmable mapping
> b) an Application specific location where CFC's reside
Ah, now I see what you mean (the only "namespace" stuff I'm fairly
with is C++ and I couldn't see how that would really apply to CF) but,
yes, programmable mappings would be very useful. Just bear in mind
that in reality they would need to be per request (as application name
etc is today).
As Roland notes, this is a commonly requested enhancement request for CF!
--
---------------
-------------------------------------
Buy SQLSurveyor!
http://www.web-relevant.com/sqlsurveyor
Never make your developers open Enterprise Manager again. ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
