As far as I can tell, this doesn't work:

Path(`/foo/<value>`) && !Host(`bar.<domain>`)

Removing the negation ("!") allows it to work.

It'd be great if negation were allowed in the syntax.

Similar to #8 it looks like the OR boolean operator (||) is not supported either.

Receiving this error when setting a frontend up in VulcanD:

route should be a valid route expression

Here's the route im attempting to add:

frontend upsert --backend mockbin --id=mockbin --route 'HostRegexp("^mockbin\..*")'

I verified my regex using Rubular: http://rubular.com/r/qQiGivbXQ4

Thoughts?

I'm having problems with the fact that expressions are sorted alphabetically, is there any reason to do this?
https://github.com/vulcand/route/blob/master/router.go#L145

Add new matcher & regexpMatcher which match against http.Request RemoteAddr value.

So we can implement weighted round robin balancing just by using this function in vulcan's frontends or listener scopes. This allows us to do graceful deployment (canary deployment?) of new versions and lets it run for a while.

Why don't you add port matcher? I'd like to change routing depending on host & port combination in vulcand

None of the docs mention how to use <matcherType:name>.