> > >I have a better question. Has anybody come up with a design > that we can > > >agree on for this? If there is no design, then we really > can't solve the > > >problem quickly. The last I saw about this issue, nobody > agreed on how to > > >fix it, or even that there was a real problem. > > > > > > > There were a few promising solutions, but all of them had one > > technical problem or another. Basically, each of the proposals > > performed well for some set of operations but poorly for at least > > one other operation that might be important to some application. > > > > Toward the end of that last round of discussions, I thus proposed > > that APR get out of the business of managing microseconds: > > > > http://marc.theaimsgroup.com/?l=apr-dev&m=102678180413988 > > > > I'm interested in hearing people's comments on that proposal. > > Doesn't that completely ignore Cliff's message early in this thread that > specifically stated that he needed microsecond resolution?
Go read the post in detail. microsecond resolution is available. It is just stored in a different field. I am +0 on the proposal pending further mastication :-) Bill
