3 ms·

sure we have. have you read through the developer docs for most API's? here's twitters: https://dev.twitter.com/docs/api/1.1 https://dev.twitter.com/docs/api/1

sure we have. have you read through the developer docs for most API's? here's twitters: https://dev.twitter.com/docs/api/1.1 https://dev.twitter.com/docs/api/1.1 its all GET and POST. this is typical.

YellowRex 13y ago
I just wrote a REST API for my company and used PUT and DELETE (Tomcat doesn't support PATCH yet). Plenty of DELETE in Stripe's API: https://stripe.com/docs/api#delete_recipient https://stripe.com/docs/api#delete_recipient Github uses HEAD, PATCH, PUT, and DELETE: http://developer.github.com/v3/#http-verbs http://developer.github.com/v3/#http-verbs Twilio supports PUT and DELETE: http://www.twilio.com/docs/api/rest/request http://www.twilio.com/docs/api/rest/request There are all darlings of the HK community with highly praised, widely used REST APIs. Have you read through the developer docs for most APIs? (edit: typo)
- ramchip 13y ago
  To be fair to the other poster, I wouldn't be surprised if 99.9% of requests were GET/POST/HEAD.
  - Gigablah 13y ago
    And 99.9% of requests are GET rather than POST, so shall we get rid of POST then?
    - shawnz 13y ago
      GET and POST already have widely observed distinctions in how they should be handled. For example, try hitting refresh on a page that was arrived at via a POST request. That behaviour is pretty much common to all browsers.
    - tericho 13y ago
      His point was that at minimum you still need a GET and POST for read and write. So comparing the numbers against bike-shed implementations is moot. Of course the number of reads will be significantly higher.
      - icebraining 13y ago
        You could write and read using just POST. SOAP is the living example of that. So I think his point is inconsistent.
dragonwriter 13y ago
Okay, here's Google Drive's https://developers.google.com/drive/v2/reference/ https://developers.google.com/drive/v2/reference/ it uses GET, POST, PATCH, PUT, and DELETE Here's (part of) the Amazon S3 API: http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketOps.html http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketOps... http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectOps.html http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectOps... HEAD, GET, DELETE, PUT, POST
- lucisferre 13y ago
  And that makes the API better because...?
  - dragonwriter 13y ago
    I'm responding here to the claim that the verbs other than GET, HEAD, and POST are generally unused in APIs. The discussion of the merits of the verbs aside from their frequency of use in APIs is on other subthreads.
buro9 13y ago
That's Twitters'. Twitter has no concept of edit for a tweet. Is it surprising then that they don't need to use PUT or PATCH?

YellowRex 13y ago

I just wrote a REST API for my company and used PUT and DELETE (Tomcat doesn't support PATCH yet). Plenty of DELETE in Stripe's API: https://stripe.com/docs/api#delete_recipient https://stripe.com/docs/api#delete_recipient Github uses HEAD, PATCH, PUT, and DELETE: http://developer.github.com/v3/#http-verbs http://developer.github.com/v3/#http-verbs Twilio supports PUT and DELETE: http://www.twilio.com/docs/api/rest/request http://www.twilio.com/docs/api/rest/request There are all darlings of the HK community with highly praised, widely used REST APIs. Have you read through the developer docs for most APIs? (edit: typo)

ramchip 13y ago
To be fair to the other poster, I wouldn't be surprised if 99.9% of requests were GET/POST/HEAD.
- Gigablah 13y ago
  And 99.9% of requests are GET rather than POST, so shall we get rid of POST then?
  - shawnz 13y ago
    GET and POST already have widely observed distinctions in how they should be handled. For example, try hitting refresh on a page that was arrived at via a POST request. That behaviour is pretty much common to all browsers.
  - tericho 13y ago
    His point was that at minimum you still need a GET and POST for read and write. So comparing the numbers against bike-shed implementations is moot. Of course the number of reads will be significantly higher.
    - icebraining 13y ago
      You could write and read using just POST. SOAP is the living example of that. So I think his point is inconsistent.

dragonwriter 13y ago

Okay, here's Google Drive's https://developers.google.com/drive/v2/reference/ https://developers.google.com/drive/v2/reference/ it uses GET, POST, PATCH, PUT, and DELETE Here's (part of) the Amazon S3 API: http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketOps.html http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketOps... http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectOps.html http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectOps... HEAD, GET, DELETE, PUT, POST

lucisferre 13y ago
And that makes the API better because...?
- dragonwriter 13y ago
  I'm responding here to the claim that the verbs other than GET, HEAD, and POST are generally unused in APIs. The discussion of the merits of the verbs aside from their frequency of use in APIs is on other subthreads.

buro9 13y ago

That's Twitters'. Twitter has no concept of edit for a tweet. Is it surprising then that they don't need to use PUT or PATCH?