Webware for Python

I've been having problems with Sessions prematurely timing out over
here and I think I've found a fix (although I'm not quite sure what
the original problem was).

I've patched WebKit.Session to have:

self._lastAccessTime = time()

as the first line in the following methods:

def value(self, name, default=NoDefault)
def hasValue(self, name):
def setValue(self, name, value):
def delValue(self, name):
def values(self):

I'm not quite sure which class is supposed to be calling awake() on
the session, but it's not happening in my code.  I also think that
making the lastAccessTime update when values are - well - accessed -
is the expected behaviour for most people.

Can we get this patched up in Webware's trunk?

vic

[Webware-discuss] Re: patching Session.py to fix premature Session invalidation From: Victor Ng <crankycoder@gm...> - 2004-10-06 21:17 I've posted a patch to SourceForge at: http://sourceforge.net/tracker/index.php?func=detail&aid=1041795&group_id=4866&atid=304866 On Wed, 6 Oct 2004 17:04:50 -0400, Victor Ng <crankycoder@...> wrote: > I've been having problems with Sessions prematurely timing out over > here and I think I've found a fix (although I'm not quite sure what > the original problem was). > > I've patched WebKit.Session to have: > > self._lastAccessTime = time() > > as the first line in the following methods: > > def value(self, name, default=NoDefault) > def hasValue(self, name): > def setValue(self, name, value): > def delValue(self, name): > def values(self): > > I'm not quite sure which class is supposed to be calling awake() on > the session, but it's not happening in my code. I also think that > making the lastAccessTime update when values are - well - accessed - > is the expected behaviour for most people. > > Can we get this patched up in Webware's trunk? > > vic >

Re: [Webware-discuss] Re: patching Session.py to fix premature Session invalidation From: Jason Hildebrand <jason@pe...> - 2004-10-08 03:15 On Wed, 2004-10-06 at 16:16, Victor Ng wrote: > I've posted a patch to SourceForge at: > http://sourceforge.net/tracker/ > index.php?func=detail&aid=1041795&group_id=4866&atid=304866 > On Wed, 6 Oct 2004 17:04:50 -0400, Victor Ng <crankycoder@...> > wrote: > > I've been having problems with Sessions prematurely timing out over > > here and I think I've found a fix (although I'm not quite sure what > > the original problem was). Hi Victor, I believe I fixed this problem back in April, and committed the fix to CVS. The problem was that Transaction was not calling Session.awake() under all circumstances. Could it be that the source tree you were using when you experienced the problem pre-dates my fix? peace, Jason

Re: [Webware-discuss] Re: patching Session.py to fix premature Session invalidation From: <vng1@ma...> - 2004-10-08 04:40 Attachments: smime.p7s      Almost certainly. My webware snapshot is from Feb 13, 2004. :) I'll grab a new snapshot and propagate it to the rest of my team over here. vic --- Don't be humble ... you're not that great. -- Golda Meir On 7-Oct-04, at 11:12 PM, Jason Hildebrand wrote: > On Wed, 2004-10-06 at 16:16, Victor Ng wrote: >> I've posted a patch to SourceForge at: > >> http://sourceforge.net/tracker/ >> index.php?func=detail&aid=1041795&group_id=4866&atid=304866 > > >> On Wed, 6 Oct 2004 17:04:50 -0400, Victor Ng <crankycoder@...> >> wrote: >>> I've been having problems with Sessions prematurely timing out over >>> here and I think I've found a fix (although I'm not quite sure what >>> the original problem was). > > Hi Victor, > > I believe I fixed this problem back in April, and committed the fix to > CVS. > The problem was that Transaction was not calling Session.awake() under > all > circumstances. Could it be that the source tree you were using when > you > experienced the problem pre-dates my fix? > > peace, > Jason >

1 message has been excluded from this view by a project administrator.