[httpapi] Byte Range PATCH with incorporated feedback

[Austin William Wright <[e-mail]>]

Hello HTTP APIs,

I published a new draft of the Byte Range PATCH I-D that I presented at IETF 116, for consideration for adoption: https://www.ietf.org/archive/id/draft-wright-http-patch-byterange-03.html <https://www.ietf.org/archive/id/draft-wright-http-patch-byterange-03.html>

Thanks for the warm response at the meeting.

I’ve incorporated feedback from the meeting, mostly clarifying or emphasizing features; and also a couple of ideas that I’ve thought of since, while working on an implementation. First, during the meeting I speculated there should be a header to specify if requests should be atomic or not, so I also added a Preference for this. (I think I could improve the terms I picked, and would welcome suggestions for something else.) And second, I added a short discussion that the patch should be able to truncate a document, since this is a simple operation, and would permit reversing an “append” operation.

For the curious, I put together a demo where you can load any HTTP resource (CORS permitting), then edit it, and preview or submit a patch that describes just the changes: https://awwright.github.io/http-progress/demo-patch-byterange-server/client.xhtml <https://awwright.github.io/http-progress/demo-patch-byterange-server/client.xhtml>

Thanks,

Austin Wright.