OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: AW: [xml-dev] RFC for XML Object Parsing

You miss the point entirely in your excitement to type about how I used the word "tag" or some other off-track subject.  ISP's we not caching back when we were all using Netscape.  ETag was added to HTTP 1.1.  This is history that I recall.   Also - as I said , you must distinguish between server side and client side caching.  Can we get back on the subject at hand?  This entire subject of HTTP caching is only to explain a similarity to the purpose and need of this "oid" and "Update Time".  I dare not ask you if you can recognize the similarity, because I asked you to comment on the UpdateTime and you got all off subject again.  Suppose we erased all analogies to similarities between this "oid" concept and other HTTP Concepts then your only comment would have been my use of the word "tag".  Don't feel obligated to comment if you don't have anything to say.  Thanks for your input sir, please have a seat and allow someone else to speak.
Anyone else - If we took caching so seriously in HTTP, why should we avoid it all together in XML?

> From: arjun.ray@verizon.net
> To: xml-dev@lists.xml.org
> Date: Sun, 23 Mar 2014 17:29:20 -0400
> Subject: Re: AW: [xml-dev] RFC for XML Object Parsing
> [Default] On Sun, 23 Mar 2014 12:11:47 -0600, Brian Aberle
> <xmlboss@live.com> wrote:
> | Call it what you may, HTTP 1.0 didn't have it. It was added to HTTP
> | because it was needed.
> I'm afraid your historical recall is faulty.
> The fact of the matter is that caching was taken seriously quite
> early. From an archive of the early years of the www-talk mailing
> list (referenced at
> http://lists.w3.org/Archives/Public/www-talk/2013SepOct/0002.html):
> http://inkdroid.org/tmp/www-talk/0237.html
> http://inkdroid.org/tmp/www-talk/0433.html
> http://inkdroid.org/tmp/www-talk/0453.html
> What eventually became HTTP/1.0 was initially named HTTP2 - because it
> was the second spec. The original spec was like Gopher, and had no
> provision for header fields at all. (When HTTP/1.0 was finally named,
> this precursor was then jokingly dubbed HTTP/0.96)
> The initial drafts of HTTP2 were by Tim Berners-Lee and Dave Raggett,
> in early 1993. The Last-Modified header date back to then, with hints
> that the HEAD verb could be used to determined the modification status
> of a document. This was superseded by Roy Fielding's "conditional GET"
> proposal in early 1994
> http://inkdroid.org/tmp/www-talk/3465.html
> This was implemented in servers (and caching servers) before the
> -ahem= market-leading browsers (a recurring tale on the web, sigh).
> And eventually, the official HTTP/1.0 spec had If-Modified-Since:
> http://www.rfc-base.org/txt/rfc-1945.txt
> _______________________________________________________________________
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS