>
> Yet, you still need to work with pattern such as:
> */Articles/{aid}/Comments/{cid}/likes*, which AFAIK, httprouter can't
> handle (correct me if I'm wrong; one of my research point leads to here:
> https://husobee.github.io/golang/url-router/2015/06/15/why-do-all-golang-url-routers-suck.html
> ).
>
> I've tried and tested out httprouter as guided
(https://gitlab.com/holloway/golang-web-tutorial/blob/master/sockets/rest/httprouter/httprouter.go).
Correction to my statement above, httprouter can work with the mentioned
pattern. Using httprouter produces:
1. A lot more cleaner code
2. Its the library is straight and easy to read as well (It took me 15 mins
to understand the library compared to 6 hours of research on self-invention
as guided in the blog)
3. It demonstrates a clearer MVVM pattern (not framework) so at least it
helps in communications and GoLang new comers.
Hence, I'm now officially throwing away my tested but not benchmarked
*parser_url* and aligned with the httprouter team, mainly due to its
benchmark and already tested codes. This exploration was an interesting
experience and thanks all.
Signing off,
Kean
--
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.
