René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Use consistent \"update\" verbs in our API based on the underlying RPC (PUT/PATCH).","articleBody":"When it comes to metadata, some apiary libraries provide \"patch\" operations, some provide \"update\" and others provide both.\n\nIn GCS API we picked the verb \"update\" for PATCH operation and we don't provide a \"replace\"/PUT\n(which exists now in the apiary world but is probably going to be removed for gRPC).\n\nI would like to avoid confusion when using different services, and suggests we always use the same\nverb for metadata \"patch\" operations and a different one for metadata \"replace\" operations.\n\nSome options for API names:\n\n|  | Patch RPC | Update RPC |\n| --- | :-: | :-: |\n| 1 | patch | update |\n| 2 | patch | put |\n| 3 | update | replace |\n| 4 | update | set |\n| 5 | update | put |\n\nOther options are welcomed.\n\ngRPC does not provide the apiary level PATCH support (it is up to the service), and One Platform\nsuggests to use HTTP PATCH for update operations that are partial _or_ non-idempotent.\n\nMy preference is option (3)\n\n/cc @mziccard @ajkannan @jgeewax \n","author":{"url":"https://github.com/aozarov","@type":"Person","name":"aozarov"},"datePublished":"2015-11-04T19:01:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/321/google-cloud-java/issues/321"}