The main difference is that J2EE sessions use session-based cookeis (i.e. they expire when the browser closes). This can be emulated with the old-school CF sessions but you have to write the relevant code into every app. Also, to make the older CF sessions more secure you need to use a UUID for the cftoken (another option in the CF Admin).
Finally, J2EE sessions allow for clustering in CF Enterprise and they also allow you to share the session scope with java servlets and JSP. On 5/15/07, Robert Rawlins - Think Blue <[EMAIL PROTECTED]> wrote: > Thanks for all your help on this one guys, > > As with Judah this is the part of ColdFusion I'm yet to really study, but it > all sounds pretty interesting. I'm sure that J2EE sessions will support my > applications, I'm not using any particularly advanced session functions, > it's just a place to store my users general data and security. -- mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:278138 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
