On Fri, Apr 23, 2004 at 09:08:28AM +1200, Sidney Markowitz wrote: > > When I suggested making the atime in Bayes two bytes instead of four by > making it coarser grained than one second, somebody (Justin?) said that > it had been tried and produced problems in handling expiry. > > Can whoever knows about this post some details? It would make such a > difference in I/O requirements to not have to update the atime field on > every significant token in every message, that I don't want to just drop > the issue without trying to solve the problems with it. I have a hard > time imagining what would be wrong with expiring tokens on a day > boundary instead of one second. >
I could definitely see folks expiring more than once a day on a busy site and that could cause a problem. Perhaps we could make it configurable, where we let the user select the buffer (1 day, 2 days, 1 week, 1 month, etc) with the default being 0. The folks who want to lower their I/O requirements can adjust the value. That doesn't solve the issue of storing the value in a two byte int, I'll have think on that one a little bit more. Michael
