At this point haven't you just built your own framework? You looked around, did some research, read a whole of documentation and decided that this set of components work well together and do what you want.
It seems to me that a framework is the exact same thing except that somebody else has compiled a list of components and then wired them up in a coherent way and hopefully provided one set of documents to explain it all. Hopefully there is also a single place to get help too. On Wednesday, September 13, 2017 at 2:50:39 PM UTC+12, Sam Whited wrote: > > Here is a list of useful components that I sometimes reach for when I > need to do something in HTTP land that requires that I leave the comfort > and safety of the standard library but don't want to get locked into a > "framework". There may be better implementations of some of these, but > the ones listed here are often "good enough" in my book: > > - https://godoc.org/golang.org/x/net/xsrftoken > - https://godoc.org/golang.org/x/oauth2 > - https://godoc.org/golang.org/x/oauth2/jwt > - https://godoc.org/golang.org/x/oauth2/jws > - https://godoc.org/golang.org/x/net/netutil (contains a method for > limiting simultaneous connections) > - https://godoc.org/golang.org/x/net/websocket (though I've heard that > some people prefer https://godoc.org/github.com/gorilla/websocket) > - https://godoc.org/golang.org/x/time/rate (rate limiter) > - https://godoc.org/golang.org/x/net/trace (request tracing) > - https://godoc.org/golang.org/x/text/secure/precis (Unicode safety) > > —Sam > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
