You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least one user used PUT without realizing it is an incomplete experiment, much more so than other experimental APIs. grpc/grpc-go#2881 (comment) (and b/217892555). That caused compatibility issues when Go improved its implementation to verify the HTTP method is POST.
I believe I heard @yashykt recently removed the GET support in C (but I failed to find the PR quickly; "get" is hard to search for). Yes, PUT probably has very low maintenance burden, but grpc dev interest in PUT is lower than that of GET, so at this point it seems best to remove the API. If we don't want to do that, I guess we can put a "DO NOT USE" message in the docs.
At least one user used PUT without realizing it is an incomplete experiment, much more so than other experimental APIs. grpc/grpc-go#2881 (comment) (and b/217892555). That caused compatibility issues when Go improved its implementation to verify the HTTP method is POST.
I believe I heard @yashykt recently removed the GET support in C (but I failed to find the PR quickly; "get" is hard to search for). Yes, PUT probably has very low maintenance burden, but grpc dev interest in PUT is lower than that of GET, so at this point it seems best to remove the API. If we don't want to do that, I guess we can put a "DO NOT USE" message in the docs.
CC @markdroth, @bdhess, @dfawley
The text was updated successfully, but these errors were encountered: