API Stability about goji

[zenazn]

Yeah, I'd like to promise a stable API at some point. I don't think that point is now, though: the project is simply too new.

This is a pretty shitty answer for people actually attempting to use Goji, though, so let me make some educated guesses as to which things are currently actually stable:

• bind on *NIX
• graceful
• param.Parse (i.e., its method signature and rough behavior. The types of errors returned might get a little more done to them)
• web.C
• the types accepted as middleware, the middleware mutation functions, and how middleware behaves in general
• the types accepted as handlers
• the semantics of route selection

Things that I'm definitely going to have a good hard look at:

• the syntax of pat-like prefix routes (e.g., "/profile/:id/*"). I'm kind of suspicious of the syntax and am starting to get cold feet about the semantics as well
• all the standard middleware implementations
• all the standard environment keys

[zenazn]

It's been a while, but I finally implemented the changes I thought I would with prefix routes (2fe5c3e).

I think this is all the API changes I've come up with during several months of use, so I think I'm about ready to declare Goji (or at the very least package web) API-stable.