I think you should be a bit careful on wording here. Doing structClear on a session will NOT timeout the session. It just removes the data in it. So for example, onSessionEnd will not fire.
On 7/17/07, Charlie Griefer <[EMAIL PROTECTED]> wrote: > Rick: > > even if there weren't any differences from a coding standpoint, the > fact that you can choose between the two still suggests that they are > different (at least different enough that the choice is there). > > J2EE sessions end on browser close. traditional cf sessions do not. > > you can time out a J2EE session via <cfset > getPageContext().getSession().invalidate()>. you'd time out a > traditional cf session via <cfset structClear(session) />. > > that there's a coding difference :) > > On 7/17/07, Rick Root <[EMAIL PROTECTED]> wrote: > > Well, the interviewer was actually asking if I used j2ee session > > variables, to which I would've quickly answered "no" > > > > But as far as coldfusion is concerned, There's only one type of > > session variables. Those are variables placed in the session scope. > > > > Whether or not they are J2EE session variables is an administrative > > setting of the server. > > > > I don't really consider them a different type of session variable, > > because from a coding standpoint, you don't really treat them any > > differently. > > > > Although he said he'd heard you didn't need to lock j2ee session variables. > > > > All I know is that when you cluster, you *HAVE* to use j2ee session > > variables in order to get them to replicate. > > > > Rick > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 beta â Build next generation applications today. Free beta download on Labs http://www.adobe.com/cfusion/entitlement/index.cfm?e=labs_adobecf8_beta Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:283906 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
