Re: [dispatch] Proposal for Per Resource Events Protocol

[[e-mail]]

Rahul Gupta <cxres=[e-mail]> writes:
> I have submitted my proposal for the Per Resource Events
> <https://github.com/CxRes/prep> Protocol as an
> Internet-Draft
> https://datatracker.ietf.org/doc/draft-gupta-httpbis-per-resource-events/

A few bits:

- Section 5.1 seems to introduce "event fields" but it doesn't provide
  any description of what they *are*.  This is particularly treacherous
  because the use of "fields" in "event fields" evidently does not mean
  exactly the same thing as "header fields" (as event fields aren't
  header fields), but are likely to have the same *names* as header
  fields, and event fields have values in some (different) way, which
  values have similar semantics to the corresponding header field
  values.

- A few fairly complete examples would help.  In particular, I *think*
  that the concept is that PREP is started by the client sending a GET
  containing the appropriate headers, then the server sends the header
  of a response containing the appropriate headers, then the first part
  of a multipart body and the first body part (containing the current
  state of the resource), then a multipart divider ... then possibly a
  delay ... then a second body part (containing the first update), then
  a multipart divider ... then possibly a delay ...  But I don't think
  this is stated clearly near the beginning, nor is a complete example
  given.

- Do you have an initial application?  It always helps to get traction
  if you have an existing need that can be satisfied, or better, two or
  three.

- There's some sort of index at the end, but it's difficult to read, and
  it appears to only be a list of places where specified terms appear.
  This doesn't add much value, since every tool a person might use to
  look at draft-gupta-httpbis-per-resource-events has a string-search
  capability.

Dale