Questionable API-Related Patents

I understand that companies file for patents to build their portfolios, assert their stance in their industry, and — when necessary — use patents as leverage in negotiations and in a court of law. There are a number of things that I feel patents logically apply to, but I have trouble understanding why folks insist on patenting things that make the web and this whole API thing work.

One such filing is patent number US9300759 B1: API Calls With Dependencies, which is defined as:

Techniques are disclosed for a client-and-server architecture where the client makes asynchronous API calls to the client. Where the client makes multiple asynchronous API calls, and where these API calls have dependencies (i.e., a result of one call is used as a parameter in a second call), the client may send the server these multiple asynchronous API calls before execution of a call has completed. The server may then execute these multiple asynchronous API calls, using a result generated from one call as a parameter to another call.

Maybe I live in a different dimension than everyone else, but this doesn't sound unique or novel, and it really just feels like folks are mapping out all the things that are working on the web and filing for patents. I found this patent while going through the almost 1,300 API-related patents in the Amazon Web Services portfolio. Many of their patents make sense to me, but this one felt like it didn't belong.

When I read these patents, I worry about the future of the web. Ultimately, I can only monitor the courts for API-related patent litigation and keep an eye out for new cases, as this is where the whole API patent game is going to play out. I'll keep squawking every time I read a patent that doesn't just belong, and when I see any new legal cases, I will help shine a light on what is going on.