Note on the wddx, we were doing the same thing. We put a to client scope in the onrequestend.cfm and to session in the application.cfm/c
This was all good until we started adding a lot of ajax calls and greatly increased the total numbed of http requests. We had all kinds of latency issues and even client db corruption from the number and size (we had rather large session structures) of write operations. This at one point was adding about 1.5 secs per request. We first moved to json serialization which seemed faster and smaller in size than wddx. Though, eventually we moved away from client vars all together and are just using session variables for all apps on our internal cluster. I doubt I'll every use client vars again, even in a cluster, and I've also learned to keep sessions as small as possible. One of our main issues with shared cf hosting are apps that have large sessions which hog resources. Came across a customer today with 100 sessions totalling about 45 MB, and that's just one example. High session timeouts are another factor in performance as well. Often seen customers requesting us to up the maximum to days, no so good :-) Byron Mann Lead Engineer and Architect Hostmysite.com On May 15, 2012 2:44 PM, "Nick Gleason" <[email protected]> wrote: > > Hi folks, > > > > With our CMS / CRM application, we are looking at moving from a reliance on > client variables towards more reliance on session variables, including as > it > relates to logins. One challenging scenario happens when a client is using > SSL for ecommerce transactions. If a user logs in, using session variables > for persistence, then goes to a page that is not in https and then goes to > a > page (e.g. an ecommerce screen) that uses https, sessions are dumped when > the site goes into https and the login can be lost. > > > > We are probably going to solve that problem by just requiring the whole > site > to go into https. However, I wanted to know if there are other good ways > to > solve this. > > > > We have solved that kind of problem in a related scenario (with attribute > scoped variables that need to survive https) by using wddx to store > variables in the client scope and then get them back from there after > moving > into https. That has worked pretty well, but feels a bit complex. > > > > As we look at expanding our use of sessions, it seems like a good time to > look at other options. So, are there other or better ways to keep session > variables alive when a logged in user goes to an https encrypted page? > > > > Thanks in advance, > > > > Nick > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:351196 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
