Home

Alright, up till now I have done fairly dirty things to get the system to work. Letting the weeds grow can be useful sometimes to help discern object boundaries.

The development style here is very typical of my current thinking. Everything at the moment is an experiment in hexagonal membranism -- only working against the surface exposed by the ports of the system.

Mostly these ports are exhibited as the public protocol for the system. They represent interactions that can happen between the outside world and the program inside the boundary.

The other thing I wanted to do was create an executable document for the OAuth specification. That aim is slightly at odds with hexagonal membranism however, as it involves exposing details that are not strictly public domain. A signature base string is a good example: it is an implementation detail that ought to be concealed from view, but because its generation is described in great detail and it is so crucial in the signing process I have left it in.

But never mind, this is an exercise, so let's just see what happens.