Hi,
I am not sure, please help:
The sizep parameter is the "remaining application data prediction" according to
OCP-Core draft.
I see some conflicts:
1. What if the agent knows that it will skip certain message parts? Does it
need to substract this skipped size from the sizep parameter? This will break
our Content-Length idea.
Or does skipping of parts not affect sizep parameter? Is this then still the
"remaining application data"?
2. What about optional parts? Should their size be added to sizep? Will again
break Content-Length trick.
3. Trailers belong to the application data. Therefore the DUM message
containing the response-header should have a sizep parameter equal to
response-body size plus response-trailer size. But this is not the size that we
can use for Content-Length correction.
4. If response-header part is sent in multiple DUM messages, only the last DUM
message contains the correct sizep value. I am concerned some implementations
will not be prepared for this case.
Putting all this together, I feel that using the sizep parameter for
Content-Length indication does not really work.
Shouldn't we better introduce a Content-Length named parameter to AMS messages
that does what we really want: Promise a length that can be used for HTTP
Content-Length header correction?
Regards
Martin