Duane Johnson

Oh, since `Patch-Length` is a REQUIRED header for a patch, it also simplifies the parser! An implementation's parser need only alternate between two states (headers/body) during parsing instead of 4...

Thinking about the names a bit more: 1. `Patch-Length` could perhaps be misconstrued to mean "the length of the content in the resource being patched". This would be incorrect, of...

A better example might also be modifying HTML from the server in an "animated" sort of way.

What about the term "Update"? An Update can optionally have a version (ID) An Update doesn't imply multiple versions An Update can be a snapshot An Update can contain a...

Is there a PR or specific proposal on this? The ".foo" syntax is preferred, IMO, because it is a more common way to specify JSON paths. For example, some common...

Both options seem reasonable. I also prefer (1).

I like this change. Does anyone have a use case where it makes sense to have multiple patch types in the same subscription, and ending the subscription and resubscribing doesn't...

I use nginx (with certbot doing the SSL configuration) in front of y-websocket and it works well.

Here is my nginx proxy setup: ``` server { listen 80 ; # listen [::]:80 ipv6only=on; root /var/www/html; index index.php index.html index.htm; server_name y.relm.us; location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;...

I just realized this explains a bug I've been seeing where exporting documents via API only work on the 2nd attempt (since the first attempt "warms" it into memory, and...