ietf-openproxy
[Top] [All Lists]

Re: what-parts-to-send-or-skip

2003-10-26 13:29:27


I think there is a misunderstanding. I do not mean an offset that
counts from the beginning of the application message but from the
beginning of the body part (request-body in request profile,
response-body in response profile). Services only interested in
headers, can use Pause-Offset: 0.

Yes, I did misunderstood. What you propose is probably better, at
least as far as HTTP and similar protocols are concerned. I just find
the naming of the parameter misleading. So let's have two parameters:
Wont-Use-Body: offset
and
Pause-At-Body: offset
both using offsets from the beginning of a message body. These NR
parameters are semantically equivalent to Wont-Use parameter and
Data-Pause message already documented in OCP Core (and you should
refer to that documentation from the HTTP draft as much as possible
instead of repeating it, IMO).

Agreed.


From processor implementation point of view, the above parameters
become meaningful when the size of headers is known. At that time, the
processor should behave as if it received a corresponding Wont-Use
parameter and/or Data-Pause message.

That seems to work for the Pause-At-Body parameter but makes less
sense for Wont-Use-Body. This parameter is not like a DUY/DUM
message that comes with Won-Use after the n bytes of a body but
can be seen as a DUM message with empty payload but Wont-Use
parameter that is sent at the very beginning of the application message
to indicate that it will not send a DUY message for the first n bytes.
It does not terminate the preservation commitment, but it tells the
OPES processor that it does not need to preserve the first n
bytes of the message.
I expect to see only one value in real life:
  Wont-Use-Body: 2147483647
to indicate that the callout service will never send DUY messages.
But maybe other scenarios can be found.

Martin


<Prev in Thread] Current Thread [Next in Thread>