Re: hash in WebID - cachability problem

On 12/3/12 7:58 AM, Nathan wrote:
> Kingsley Idehen wrote:
>> On 12/3/12 5:56 AM, Henry Story wrote:
>>> We still have to see what the issues are here. It seems that the 
>>> cacheability problem pointed out by Nathan
>>> would affect all JavaScript applications, not just tabulator
>>>
>>> [[
>>>
>>> RFC 2616 says:
>>> "The 303 response MUST NOT be cached, but the response to the second 
>>> (redirected) request might be cacheable."
>>>
>>> HTTPBis says:
>>> "A 303 response SHOULD NOT be cached unless it is indicated as 
>>> cacheable by Cache-Control or Expires header fields."
>>>
>>> Of course most tooling will not cache 303s as it's been a MUST NOT 
>>> for 13+ years.
>>> ]]
>>>
>>
>> You cache data.
>>
>> User agents don't cache entity names.
>>
>> Using DBpedia as an example, you don't cache 
>> <http://dbpedia.org/resource/Linked_Data>, you cache: 
>> <http://dbpedia.org/page/Linked_Data>, assuming the HTML 
>> representation of the entity description is what you are interested 
>> in. Same applies to all the other representations of the description 
>> of: <http://dbpedia.org/resource/Linked_Data> .
>
> Correct, the issue people note, is that you still have to do a GET on 
> <http://dbpedia.org/resource/Linked_Data> in order to get the 303 URI, 
> that second URI can then be loaded from cache, so it involves at least 
> one HTTP GET each time, even with caching.
>
>
Depends on the apps Linked Data exploitation logic :-)

An Entity Name in this case is just an indirect route to its 
description, same applies to the Entity Description Document Address. 
Thus, an application can make a decision about which "route to data" it 
works with.

The same issue arises in the ODBC or JDBC realms, I can use a connection 
string or a data source name to access data in an RDBMS via a compliant 
driver/provider/cartridge. My ODBC/JDBC application decides how this 
affects the kind of user interaction it seeks to deliver.

This is one of those "horses for courses" issues that AWWW handles well, 
once application developers tap into it etc..


-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen