Added Travis CI definition file.
Added docs to FSM state functions
Added missing docs for FSM state functions
Remove WS after doc
Fixed bug where all is-authorized? responses authenticate.

Only returning an actual boolean true should result in authentication,
this has been fixed.
Incremented the version number for release.
Replaced usage of standard Java Date calls with Joda time.

As itoshkov[0] pointed out issue #4[1], SimpleDateFormat isn't thread
safe. This was a dumb mistake on my part. I've replaced all of the
code that relies on the standard Java date functions with calls to
thread safe Joda time calls.

If you were returng java.util.Date instance in your callback functions
these will still work, behind the scenes Bishop will pull the backing
long time and use that to create a new Joda DateTime.

[0] https://github.com/itoshkov
[1] https://github.com/tnr-global/bishop/issues/4
Updated the version number in the README.
Altered the way node N11 works to better handle create failure.

Node N11 assumed that the creation of a new object was always
successful, this is a mistaken assumption. The logic in this node now
checks to see if the handler function returned it's own status code,
if that is the case then that code is used instead of a 303; if we're
not returning a 303 then the "Location" header is also removed.

This will let you catch exceptions in your handler methods and return
your own status and body content, for instance something like...

  {:status 409 :body "Change would introduce conflict"}
Incremented version number for release.
Fixed bug in the README file.
Fixed problem with the root route "/" not matching wildcard.

The root route tokenizes to an empty vector ("[]") and the route logic
wouldn't match that to the wildcard route ("[*]"), this would cause a
status 404 to be returned to the client. I added additional logic to
ensure that an empty URI would be mapped to the wildcard route.

After revisiting the [Webmaching dispatch
documentation](http://wiki.basho.com/Webmachine-Dispatching.html), it
looks like this is the only way to match the root of the URI
namespace; that is this is the expected behavior.

I also added some tests to catch any future bugs in the routing code.

This was reported on [issue
#5](https://github.com/tnr-global/bishop/issues/5).
Added a "raw-handler" to enable other routing libraries.

The "handler" function expects a Bishop style routing map and returns
a Ring handler that will route and handler incoming requests. If you
want to use another routing library, you may use the "raw-handler"
function; this returns a Ring handler that simply applies the incoming
request to the provided Bishop handler. See the test/core.clj file for
example usage.
Updated the README to mention the new "raw-handler" function.
Fixed issue where headers were lost during processing.

There was a bug where existing response headers where being lost when
the body was appended to the outgoing response.
Added a new route ("[]") that maps to the URI namespace root.

You can now use the empty set to match an incoming URI that has no
tokens, that would represent the root of the URI namespace.
Incremented the version number for release.

I also moved to Leiningen 2.
Merge branch 'state_docs' of https://github.com/jolby/bishop
Updated the README with a Moustache example.
Change to keep external example routing libraries consistent.