Interesting post related to the GRDDL issue

http://lists.w3.org/Archives/Public/www-archive/2008Jun/0105.html

"""I have tried in a
few venue in W3C to get a decision on whether or not W3C should bundle
up a catalog and work with OS vendors on getting it out.  During a
project review call on Systems Team projects Tim suggested bringing to
TAG.  Tim sees it as already handled in HTTP RFC based on caching
directives.  Unfortunately many HTTP implementations are far from
complete and I think it is unrealistic to think we can get that fixed
in the wide range of libraries and clients.  What I have to contend
with is an ever increasing strain on our infrastructure and in
addition to our defense strategies need a long term solution to the
problem.  One planned defensive strategy will adversely impact a
considerable amount of XML processing applications."""

Thus, there are concerns at the system level about the general "put  
code or code like things for downloading" strategy and the standard  
response "Caching!" turns out to be not effective in the current  
infrastructure.

I'll note that it's much easier to add something later if demand and  
systems improvements warrant it than to remove something we put up  
(or even fix such a thing). In the latter case we risk breaking  
applications that depended on downloading.

Cheers,
Bijan.

Received on Wednesday, 18 June 2008 09:18:58 UTC