Re: Resolving IRIs for resource documents in SVG Tiny 1.2

On Thu, May 15, 2008 at 5:15 PM, Helder Magalhães <
helder.magalhaes@gmail.com> wrote:

> > This seems to imply that if I have a document that contains many resource
> > references with the same relative URI, I have to perform an HTTP
> transaction
> > for each one to see if any of them result in a redirect. Wouldn't it make
> a
> > lot more sense to use the pre-redirect URI as the dictionary key, so I
> can
> > avoid a lot of network transactions?
>
> Although at a first glance I was tempted to agree with you, after a
> more through analysis I believe the behavior proposed by the
> specification is probably the more appropriate. In a stateless,
> non-persistent process, your approach seems to make more sense but, if
> one uses an gateway-like URI which is redirected to a final location
> depending on state, than this can become problematic. Note that this
> is labeled "counterexample", not to be taken as an good/advised URI
> usage pattern (at all)! :-)


I don't understand this at all. No-one could write a reliable application
that depends on some loads of a resource URI returning one redirect and
other loads of the same resource URI *from the same controlling document*
returning a different redirect, because the spec does not say when each load
happens (nor should it).

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]