Less REST, more hypermedia

From an entry into the REST-discuss mailing list:

We all know, many APIs and some frameworks labelled with the term “REST”, do
not support hypermedia (or less so called RESTful) mechanisms.
The term is (andlikely will be) very overloaded in the IT industrie.

I think, it is time to push forward terms like “hypermedia service/API” or
“hypermedia-aware client”. Instead of saying “hey i have a RESTful API”, tell
the people “i have a hypermedia API!”.

and my point:

I thought I was the only one saying “hypermedia-aware clients”.
That’s what I’m already doing since some months: since the REST term has been raped during the last decade I am now talking about HTTP (doh) and Hypermedia API.

It’s quite disappointing, but you’ll notice that a few people will ask you “why hypermedia” or “why not REST”, so, at least, they’re gonna dig a bit about that.

Hi there! I recently wrote an ebook on web application security, currently sold on leanpub, the Amazon Kindle store and gumroad.

It contains 160+ pages of content dedicated to securing web applications and improving your security awareness when building web apps, with chapters ranging from explaining how to secure HTTP cookies with the right flags to understanding why it is important to consider joining a bug bounty program.

Feel free to skim through some of the free chapters published on this blog and, if the content seems interesting enough to you, grab a copy on leanpub, the Amazon Kindle store, gumroad or simply checkout right down below!

Buy the Web Application Security ebook for $9.99

In the mood for some more reading?

...or check the archives.