Re: (Dis)Proving that 303s have a performance impact.

On 16.02.13 19:48, Henry Story wrote:


> Ok, so we need to compare like with like, in order to be able to have
> an expermiment. So we put ourselves in a user's shoes. He has to
> choose between either hash WebID, or a 303 WebID . He has the same
> information to publish in both cases
> 
> Hash:          http://joe.example/hash/joe#me Non Hash:
> http://joe.example/resource/joe
> 
> So we have the WebID and we need to get the WebID Profile document
> [1]. Let us say the Profile document is of size S .

Why on earth do I *have* to do 303 redirects in the second version? If
the client does proper content-negotiation I simply give him RDF back on
the first request.

cu

Adrian

-- 
Adrian Gschwend
@ netlabs.org

ktk [a t] netlabs.org
-------
Open Source Project
http://www.netlabs.org