W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1998

Re: Non-order processing in persistent connections

From: Uwe Danz <ud4@irz301.inf.tu-dresden.de>
Date: Mon, 18 May 1998 15:20:35 +0100 (BST)
Message-Id: <356042F6.159E@irz.inf.tu-dresden.de>
To: HTTP-WG <http-wg@cuckoo.hpl.hp.com>
Cc: ud4@irz301.inf.tu-dresden.de
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/124

Zhou Kang wrote:
> In fact, we can make some minor alteration to http server's
> performance. For example, we can add a header to the messages to
> indicate the request/response pair, something like 'Request-ID'. A
> client may create a unique digital ID for every request to the same
> server ,  then the server can return responses with this ID or without
> but use the same order. To name this mechanism , I call it as
> 'non-order processing'.

I work on a project for anonymous WWW access. It will base on HTTP/1.1
If you send a *big* packet through a MIX-Net (like Mixmaster, can
only work with a constant block size) a Cache-Proxy must connect the
parts. You can use the Content-Range Field but if some anonymous users
the same Range than they will get wasted data.
So we need also a Message-ID or 'Request-ID'.
This Message-ID should be defined for Request and Response and
*randomly* choose by the client/server. If a server, (user?),
proxy or MIX detect a collision
than a warning or error can be response to the client (may be

Uwe Danz
(my English is too bad: same mistakes corrected)
Received on Monday, 18 May 1998 08:31:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:22 UTC