how can multimethods serve as handlers ? annoyed wrapping them in functions 😣

Multimethods are simple clojure functions, so yes, you can, but it need to receive request and return response

And you may need to make some routes to it ["/foo" :get my-mm :route-name ::mm] ["/bar" :get my-mm :route-name ::mm*]

@zallin You probably have to supply a route name in order to make the routes unique, too.

when using mm as handler i get an error "You're trying to use something as an interceptor that isn't supported by the protocol; Perhaps you need to extend it?"

Oh! That's interesting. I'd call that a bug. Would you be willing to file an issue?

yes no problem

will do later this evening

Thank you.

is it possible to combine router instances? ex have a router based on map tree that contains a leaf with linear and another branch at some level using map tree?

Yes!

just wondering, I don't really need this but I could see it used

woa

Routers are just interceptors

So you can create a router then use it as an interceptor on another route

that's super cool

I just wrote a bit about that in a new guide: http://pedestal.io/guides/what-is-an-interceptor#_some_practical_applications

I must say that route lib is really impressive, probably deserves more attention

actually I have a use case for it now that I think of it: i might have to switch to linear router on some cases where there is ambiguity with other routers: ex /foo/:id/ followed by a /foo/bar/ route

trying to see if I can port what we have now over to pedestal/route

Yeah, I’ve got a similar case. The API was defined and released long ago. So we’re kind of stuck with the linear router

But so far the performance has been good enough that we didn’t get fancy

and to make it more difficult it's not on pedestal, we do use interceptors tho

another gem of a lib

That’s interesting. I haven’t heard of anyone doing that before. What are you using to accept HTTP requests? And what are you using for routing now?

jetty 9 but we have a lot of internals that rely on old tricks and we do things differently with ws

ahh for routing: moved from clout to bidi recently

but bidi is a bit resource hungry it seems

and there are some bits I d prefer different

So you write bidi handlers that call interceptor chains?

yes more or less. we have a resource abstraction that can load an interceptor chain and use it

we have doc & specs on top of it

Nice

a bit like yada, but somewhat different

response spec, request spec etc

I will have to play with the route mixing tomorrow, I hope this can be written in a somewhat declarative way without having to mess with interceptors too much

Good luck. Let us know how it turns out

will do

now that I think of it I could cheat with nginx

probably easier than nesting routers and whatnot. I would just rewrite/proxy the ambiguous routes to other paths that are resolvable with non linear routers without relying on ordering