#2346: Visit expires even though the user had accessed before expiry time
-------------------------+--------------------------------------------------
Reporter: mitsuru.oka | Owner:
Type: defect | Status: new
Priority: low | Milestone: 1.x
Component: TurboGears | Version: 1.0.8
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
On following condition, visit may expires even though the user had
accessed before expiry time T2+60.
* app.cfg: visit.time = 60
* User first accessed at T1. The expiry time should be T1+60.
* User second accessed at T2 = T1+50 < T1+60. This update the expiry time
that should be T2+60.
* User third accessed at T3 = T2+20 < T2+60. However, this often cause
the visit expire.
This is because (SqlObject|SqlAlchemy)VisitManager does not check
self.queue cache before lookup visit_class data source, which has expired
visit record until self.update_queued_visits will be called.
--
Ticket URL: <http://trac.turbogears.org/ticket/2346>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
