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

On 18 Feb 2013, at 14:03, Jürgen Jakobitsch <j.jakobitsch@semantic-web.at> wrote:

> hi,
> 
> cooluris [1] holds a lot of info, you might want to consider reading it.
> 
> please also check my suggestion for this issue [2]
> 
> wkr turnguard
> 
> [1] http://www.w3.org/TR/cooluris/

Thanks. That is indeed an interesting resource.

Unsurprisingly the section right thereafter supports the point a number of us have been making.

[[
When using 303 URIs for an ontology, like FOAF, network delay can reduce a client's performance considerable. The large number of redirects may cause higher latency. A client looking up a set of terms through 303 may use many requests, even though the first request has already loaded everything there is to know.
] http://www.w3.org/TR/cooluris/#choosing] 



> [2] http://lists.w3.org/Archives/Public/public-webid/2013Feb/0196.html
> 
> 
> On Mon, 2013-02-18 at 08:52 -0400, Michael Hackett wrote:
>> On 18 February 2013 05:03, Mo McRoberts <Mo.McRoberts@bbc.co.uk>
>> wrote:
>>        On the other hand, somebody who knows 'enough', though not a
>>        lot of SemWeb, may well look at the examples, see no *obvious*
>>        reason for the fragids, see no explanation of why they're
>>        there, and knowing about them from HTML figure they're just a
>>        stylistic nicety. The fact is that in RDF fragment identifiers
>>        in URIs are a lot more important than people are used to
>>        outside of this realm.
>> 
>> 
>> ::raises hand:: Yep, that's me! Or was, until recently. When I started
>> reviewing the WebID spec last year, I did not understand the reason
>> for the hashes, and found no explanation for them in any of the
>> material. I was looking at the spec as a way toward a more usable
>> Internet-scale security system and had pretty much *zero* experience
>> with SemWeb concepts. I think I'm starting to get it :-), but I still
>> don't think it should be a prerequisite, given that WebID can apply
>> equally well outside that space.
>> 
>> And I also agree that some non-normative background information and
>> implementation or usage guidelines are welcome even in a spec, or in a
>> primer document that is linked to from the spec. However, if they make
>> recommendations, I would like to see the justification given, or
>> referenced from another accessible source, so I can understand the
>> reasoning behind it.
>> 
>> 
> 
> -- 
> | Jürgen Jakobitsch, 
> | Software Developer
> | Semantic Web Company GmbH
> | Mariahilfer Straße 70 / Neubaugasse 1, Top 8
> | A - 1070 Wien, Austria
> | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22
> 
> COMPANY INFORMATION
> | web       : http://www.semantic-web.at/
> | foaf      : http://company.semantic-web.at/person/juergen_jakobitsch
> PERSONAL INFORMATION
> | web       : http://www.turnguard.com
> | foaf      : http://www.turnguard.com/turnguard
> | g+        : https://plus.google.com/111233759991616358206/posts
> | skype     : jakobitsch-punkt
> | xmlns:tg  = "http://www.turnguard.com/turnguard#"
> 
> 

Social Web Architect
http://bblfish.net/