>>>> "Eoghan" == Eoghan Glynn
<eoghan.glynn(a)gmail.com> writes:
> Well, I think they should remain for a while longer (but perhaps
> not in the powershell/windows2008 implementation of this API).
Eoghan> The shortness of the "short period" of retention is largely
Eoghan> determined by memory pressure. We use a SoftReference-based
Eoghan> cache that won't explicitly evict the Action resource for
Eoghan> two hours as currently configured, but will allow it to be
Eoghan> reaped before that if necessary (at the discretion of the
Eoghan> garbage collector).
> I do not like the redirect: it should just fail with 410 Gone.
Eoghan> The idea of the redirect was to capture the following idea:
Eoghan> "we no longer know the outcome of this individual action,
Eoghan> but the current state of the resource may give you a clue as
Eoghan> to what the outcome may have been".
I think that the client can go GET the data it needs, I think the
redirect is simply confusing. Having a clearer reply does not change
the number of round trips, etc. but may help client implementations that
use a library where redirects get followed automatically.
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr(a)sandelman.ottawa.on.ca
http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <
http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.