On Thu, Apr 22, 2004 at 04:36:12PM -0400, Theo Van Dinter wrote: > On Thu, Apr 22, 2004 at 03:07:21PM -0500, Michael Parker wrote: > > Curious, should the atimes be updated before calculating the expire > > delta? > > Umm. It depends? ;) > > The problem I was trying to solve there is the "relative handful of tokens > are in the future" issue, which causes expiry to not function properly. > In that case, we're not going to expire the future tokens unless we can > do a normal expire based on newest==current anyway, so there's no issue. > > If, however, the problem is "relative lots of tokens in the future", > then we'll be in the same "can't expire" state. IMHO though, the > solution for that is to blow away the DB and start over, since the 3.0 > code already should stop new tokens being added in the future, so we're > really only talking about people who currently have the issue.
Ok, I'm cool with the, handle the few anomalies. I was just making sure you weren't thinking about the really screwed up case which would never get hit due to the expire delta. No prob then. Michael
