#2346: Visit expires even though the user had accessed before expiry time
--------------------------------+-------------------------------------------
Reporter: mitsuru.oka | Owner: chrisz
Type: defect | Status: new
Priority: low | Milestone: 1.0.x bugfix
Component: TurboGears | Version: 1.0.8
Severity: normal | Resolution:
Keywords: needs patch, visit |
--------------------------------+-------------------------------------------
Comment (by Chris Arndt):
Replying to [comment:6 chrisz]:
> Dictionary lookups are thread-safe, so we don't need a lock.
I see you look up the `visit_key` in `self.queue` first, so the race
condition I was thinking would not occur.
> If I mention the new setting in the TG 1 doc wiki and add a changelog
entry, that would be sufficient, I suppose?
Yes.
--
Ticket URL: <http://trac.turbogears.org/ticket/2346#comment:7>
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
-~----------~----~----~----~------~----~------~--~---
