If you do give it a read, you'll find that his paper isn't about "shoehorning into HTTP". Actually, the title is pretty clear: _Architectural Styles and the Design of Network-based Software Architectures_. After doing a great job of classifying different types of problems and possible solutions to these problems, Dr. Fielding describes REST as a solution to a particular kind of problem. To quote (from his blog):
> REST is intended for long-lived network-based applications that span multiple organizations. If you don’t see a need for the constraints, then don’t use them.
It's fine if you don't want to use REST, but it's obvious from your comment that you don't understand what REST is or when you might use it.