A quick post before continuing with Rx and laziness on Sunday…
I’ve recently read Restful Web Clients, by Mike Amundsen, of REST fame.
We (Alex and me, mainly) are developing a Hypermedia producer/client for Liferay and this book inspired some of the work in the producer before I joined the effort.
The book seemed like a great fit for the client project because it basically covers how to develop a client with hypermedia from the scratch… but in the end, it wasn’t as interesting as I thought.
Don’t get me wrong, the book is thought-provoking for someone that doesn’t know anything about hypermedia (as myself) because the explanation about why hypermedia is important and how we are just using a small part of the theory or ideas behind REST are very interesting.
Gripes with the book
I felt that the book didn’t have much apart from the hypermedia and formats explanations (that were great and I definitely understand the pros and cons of each format) but that’s all. I don’t think I know much about restful web clients right now or how to implement them apart from some small concepts.
I also feel that all the solutions have too much code. It’s nice to have a representor pattern (strategy) that lets you create several representations of your data in the different hypermedia formats but also means a lot of code to convert back and forth the intermediate representation.
I hope no-one encounters the same situation of the book, implementing the full code for the producer and client for 4 or 5 different JSON formats.
And the end result… I can’t fathom a web that is completely auto generated and doesn’t need to customize the layout, styles or whatever. But maybe that’s me.
I’ve rated it 4 stars of 5 in Goodreads. Yeah, I know.
But I didn’t know the hypermedia formats and why there are important and the OAA challenge (support updates and information about Objects, Actions, and Addresses) was nice.
If you already know HAL, Siren or Collection+JSON, skip this one.