Re: [go-nuts] RFC: Blog post: How to not use an HTTP router

I like the notion/notation of a resource graph and will use it in the future :) On Mon, Jun 19, 2017 at 12:31 AM, Kevin Conway wrote: > > That being said, having access to easy-to-use, parameterized routes makes > things much simpler IMO. It cleanly separates the

Re: [go-nuts] RFC: Blog post: How to not use an HTTP router

If I understand correctly, you're describing a simplified version of https://twistedmatrix.com/documents/current/web/howto/using-twistedweb.html which provides the concept of "path" by having a system that generates a graph of resource nodes than can be rendered. Routing to any specific endpoint

[go-nuts] RFC: Blog post: How to not use an HTTP router

Hey gophers, in an attempt to rein in the HTTP router epidemic, I tried writing down a) why I think *any* router/muxer might not be a good thing to use (much less write) and b) what I consider good, practical advice on how to route requests instead. It's not rocket science or especially novel,