TODO:
+ Make content-type available.
+ Make sure multipart/form-data works (not sure?).
+ Clean up recent code additions.

All that was missing in 574c33c27e was a
way to retreive the values of our fuzzy matches.

TODO: Make the collected vars available to the handler words.

TODO:
+ set appropriate MIME types

TODO:
+ file-serving if no user-defined routes match. Search "public/" dir
unless otherwise specified by user.
+ query arguments
+ PUT, POST, DELETE
+ templating
+ fuzzy-/pattern-match-enabled user routes (e.g., /something/*/wildcard)?

The aim is to try to avoid polluting the global wordlist with routing
functions.

The alternative would be to have users simply define words that match
their routes, e.g.:
```
: 1991/hi
    ( some definition of hi's handler )
    ;
```

I'm still not entirely convinced that the above method isn't a better
solution.

First, define a user-facing word that takes a port and subsequently
starts the server (using gforth's unix/socket.fs).
Second, start defining a user-facing word for specifing routes and their
handlers.