This part four (0-based) of my series about REST, the mistakes people often make and some ideas of mine. This post on talks about taking advantage of resource representations in a javascript client. This is somewhat related to my other REST post, where I argue that when resources are properly identified and actually linked is should be possible (and beneficial) to ditch client URL routing.

Read on →

Previously, in my first #dajsiepoznać post, I wrote about how I’ve been trying to create wikibus.org, the public transport encyclopedia. Sadly, Most of that development has been more of blind technology exploration, learning and very little delivery. Now, I’m going forward with renewed strength, and I’d like to share more details about the idea behind the project.

Read on →

In the fourth part of my REST series I will expand the idea of links. Links are just a stepping stone no matter how important. Simple links aren’t enough for the client to interact with the server. After all how is it going to know when to POST and when to PUT or what are the required parameters and request bodies. This is where affordances come into play. It means that the server should include all information the client needs. Just as defined by the self-descriptive constraint.

Read on →

Instructions for setting up Babun (zsh) as Webstorm terminal. I’ve recently been shown Babun and having it replace GitHub for Windows shell in Webstorm was the last piece of my happiness. The tricky part was to have it open in the current working copy and not the default home path.

Read on →

This is the second post in a series about REST, where I intend to debunk some commonly repeated mistakes and bad advice for practitioners of RESTful services. The central, and agreeably most important element of any API, is the resource. On the Web resources are identified and addressed by URLs. REST defines some clear rules about these identifiers, yet we so commonly break them. Let’s see how this happens and what are the consequences.

Read on →