http - Doubts on the correctness of Microsoft Azure Multimedia Services REST API -
the azure api claims rest api. found while patterns , sample implementations , verbs in rest, when inspecting in (supposedly) rest api reference, seem have invented new verb canceljob
, altering internal state via http get
get https://media.windows.net/api/canceljob?jobid='url-encodedvalue'
this seems contradict best practices, shall implemented jobs
resource , delete
or correct way too?
delete /api/jobs?jobid='url-encodedvalue'
or even?
delete /api/jobs/jobid
rest has become buzz word people use api works on http. api appears people call rest level 1. level 1 means use http transport mechanism only. doesn't respect of rest constraints http designed for. don't think it's fair call these apis rest @ all, many still because rest popular , business/marketing people able have rest api. suspect case api because architect(s) of api put no effort whatsoever following rest principles.
Comments
Post a Comment