See Why HATEOAS is useless and what that means for REST.

The article provides a background leading up to these observations:

• There are very few good tools to create a REST API using this style
• There are no clients widely used to consume these types of APIs

The "useless" in …

Lazyweb: Django REST Framework vs. Tastypie. Thoughts? #django — Joe Dougherty (@modusjonens) February 17, 2014

Unit testing RESTful web services is rather complex. Ideally, the services are tested in isolation before being packaged as a service.

However, sometimes people will want to test the "finished" or "integrated" web services technology stack because (I suppose) they don't trust their lower-level unit tests.

Or they don't have …

Wow. Just wow. See "LANGSEC explained in a few slogans". Short, easy-to-grasp explanation of why complex protocols create new problems. I'm happy with REST and the stack of stuff under it (HTTP, TCP/IP, etc.) Once upon a time (2001), I invented by own version of a RESTful protocol outside …

I have slowly grown to love RESTful web services.

I was asked about a nearly empty section in the code repository labeled "Java client".

"Yes," I said, "it's a place-holder for a Java package that includes classes to wrap our RESTful web services."

"Really?" I was asked, "Why? We use …

It seems so simple: use the HTTP Digest Authorization with the Quality of Protection set to "auth".

It's an easy algorithm. A nonce that encodes a timestamp can be used to be sure no one is attempting to cache credentials. It's potentially very, very nice.

Except for one thing: Apache …

REST is cool because there's less protocol there -- little more than HTTP and some kind of representation for objects (XML, JSON or whatever.) It seems to me that REST with JSON is a very lightweight approach to implementing web services. Doing this in Python further trims down the technology stack …