[Zope] sessions in the presence of conflicts

[Dennis Allison]

Hi Davids.  Thanks for your note.  I remember your post. 

No, I have not used HappySession although we looked at it when we started.  
When we started development, sessions had just become part of the standard
release Zope and we decided that in the long run we'd be better off using 
the release product.

As I've said in other posts, we use the session mechanism fairly heavily.  
We have O(200) simultaneous interactive users each of whom has 40 or so 
session variables which maintain the dynamic state of their instance.  
Nearly every substantive operation touches one or more session variables.
Everything works most of the time,  but the error frequency is high enough 
for it to be of concern.

I'm a bit cautious about moving to another sessioning system on a 
sizable production system running 24x7.  

> >  
> >
> Dennis,
> Im only curious and this is no recommendation ... and I asked this on 
> the list maybe a year ago (and got zero reponses)
> 
> Have you given "HappySession" a try?  Has anyone? I've never had a 
> problem with it, but then its never been under much load and is no 
> longer actively supported (least last time I checked).
> 
> I converted back and forth between Zope SESSION and HappySession (for 
> reasons of  legacy code).  Their interfaces have just few differences, 
> e.g., HappySession['this'] returns None (if 'this' is not a key) and 
> SESSION raises an exception.  That type of thing.
> 
> HappySession  does not read/write to zodb (if I recall it stores session 
> data in RAM (session) cookies).  I just do not know if its otherwise up 
> to your requirements.
> 
> All best,
> David
> 
> 
> 
> 

--