If your business logic is in the client, and you need a backend data API, HTTP is an option. Just don’t call your static URI API “REST”.
5
18
1
12
@stilkov a little late to change HTTP API culture isn’t it? ;-)
1
1
Replying to @pvblivs
@pvblivs I don’t think so, now is the perfect time. There’s a lot of adoption and a lot of interesting challenges ;-)

Oct 12, 2015 · 8:25 PM UTC

1
Replying to @stilkov
@stilkov or leave the REST field and pick a new name. I fear the name has become too generic as everyone forgot about the meaning
1
@pvblivs Tempting, but I disagree: REST is one of the very few terms that actually has an authoritative definition. No need to give up :-)
1