>- see footer for list info -< This may seem an "out of the box" suggestion, but you could redeploy the app onto the J2EE edition of CFMX, where you can then leverage the fact that the underlying J2EE server may offer persistence of sessions itself. Both JRun, WebLogic, WebSphere, and even Tomcat offer mechanisms to persist sessions to disk and some to even replicate them across a cluster in memory (no sticky sessions). The benefit then is that you would not need to change your CFML code referring to sessions to refer to client vars instead. By using the "use j2ee sessions" option in the CFMX admin, you would be telling CF to give up control of sessions to the underlying J2EE server. (You can use that already today on the standalone versions of CFMX, but the underlying JRun as implemented doesn't expose support for persistence of sessions, if I recall. If I'm wrong, that's an even easier answer, but I think we'd have heard about it a lot if it was possible.)
Of course, redeploying onto J2EE may seem a daunting task, but it's really not. I wrote a couple of articles about it in the CFDJ a couple years ago: Making the Case for CFML on J2EE http://coldfusion.sys-con.com/read/44481.htm CFML on J2EE: Easy as 1-2-3 http://coldfusion.sys-con.com/read/45338.htm While at the time the 2nd article focused on BlueDragon and its advantage for deploying onto J2EE (over CFMX, which while it could it had not been as straightforward in CFMX 6 or 6.1). Still, since then CF7 has improved that stuff quite a bit so it's worth considering. If you don't have 7, you can indeed still deploy CFMX 6/6.1 on J2EE. It's just not as straightforward as 7 or BD/J2EE. /charlie http://www.carehart.org/blog/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marketsuite Support Sent: Monday, August 07, 2006 11:25 AM To: [email protected] Subject: [CF-Dev] Managing Session State in DB >- see footer for list info -< Hi All, I have been doing some research on the best way to handle session states because I hear there is a problem with sticky sessions and super-proxies, it seems that the most scalable option is to store the session data in client variables in the database. I am trying to get my head around How to implement this as my site uses session variables across the board. Do I have to re-model the application To use client variables or is there another way? Also any information or advice anyone has on this would be greatly Appreciated. Thanks in advance Chris Poole _______________________________________________ For details on ALL mailing lists and for joining or leaving lists, go to http://list.cfdeveloper.co.uk/mailman/listinfo -- CFDeveloper Sponsors:- >- Hosting provided by www.cfmxhosting.co.uk -< >- Forum provided by www.fusetalk.com -< >- DHTML Menus provided by www.APYCOM.com -< >- Lists hosted by www.Gradwell.com -< >- CFdeveloper is run by Russ Michaels, feel free to volunteer your help >-< _______________________________________________ For details on ALL mailing lists and for joining or leaving lists, go to http://list.cfdeveloper.co.uk/mailman/listinfo -- CFDeveloper Sponsors:- >- Hosting provided by www.cfmxhosting.co.uk -< >- Forum provided by www.fusetalk.com -< >- DHTML Menus provided by www.APYCOM.com -< >- Lists hosted by www.Gradwell.com -< >- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<
