- From: Louis Theran <louis.theran@nokia.com>
- Date: 3 May 2000 15:26:11 -0700
- To: www-p3p-public-comments@w3.org
I wrote:
>> Section 2.4.4 refers to the `asynchronous nature' of HTTP messages.
>> This description is confusing, seeing as HTTP is a synchronous,
>> pipelined protocol. Also, it isn't really clear when it is
>> permissible for a client to ignore the server's caching directives
>> or why this is necessary.
Martin responds:
> This section ("Authoritative caches") has been removed. In its place,
> a paragraph in section 2.3.2.1 has been added:
>
> Note that it is impossible for a client to accurately predict the
> amount of latency that may affect an HTTP request. Thus, if the policy
> reference file covering a request is going to expire soon, clients MAY
> wish to consider warning their users and/or revalidating the policy
> reference file before continuing with the request.
>
> We believe that this captures the original intent behind the section
> you referenced, without making inaccurate claims about the nature of
> HTTP.
Received on Wednesday, 3 May 2000 15:24:01 UTC