best practice on session variable persistence and ssl?

Funny you should mention high session time outs. I was given a task by a friend to look at, on something that I did many years ago. Since then they had another developer come in make some changes and the server fell over about 5 times a day, when I looked at it, the session was set to 2 days, I was like WTF... Change it back to what I had set it at 6 years ago, and 8 months later it hasn't fallen over once. -- Regards, Andrew Scott WebSite: http://www.andyscott.id.au/ Google+: http://plus.google.com/108193156965451149543 On Wed, May 16, 2012 at 3:12 PM, Byr > > 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" <n.gleason@citysoft.com> wrote: > >