On Tue, Jan 13, 2009 at 8:10 PM, Justin Erenkrantz
<jerenkrantz_at_apache.org> wrote:
> On Tue, Jan 13, 2009 at 5:23 PM, Eric Gillespie <epg_at_pretzelnet.org> wrote:
>> In what universe does "latest" mean "the value I cached when you
>> created this ra object an hour ago"?
>
> No matter what value you fetch from the server, excepting that it
> represents a lower-bound on the true value, the value *must* otherwise
> be considered immediately invalid anyway. I believe whether it's
> out-of-date by an hour or a minute or a second is largely immaterial
> in the larger scheme of things. If code is making assumptions that
> the latest revision value is accurate, then there's likely deeper
> issues in the code. -- justin
Eric already gave (IMO) a valid use-case -- a daemon which opens an
ra_session and "polls" the repository every 2 minutes. Like a
buildbot, for example. There's nothing pathological about such a
program: it's not depending on the assumption that each polled value
can't possibly be out-of-date at all, but it *is* assuming that it's
not more than 2 minutes out-of-date, which is completely reasonable.
Received on 2009-01-14 06:12:54 CET