/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 damienradtke.com
Nomad Task Versioning · Version 7.0
| | lanie.dev
parsing a form
13.2 parsecs away

Travel
| | So you want to parse a form. You have your handler, and you're getting data passed in through the request. 1 2 3 4 5 package example func Login(w http.ResponseWriter, r *http.Request) { // hi (: } The next step is to parse the form on the request. 1 2 3 4 5 6 func Login(w http.ResponseWriter, r *http.Request) { var err error if err := r.
| | www.alexedwards.net
Golang Response Snippets: JSON, XML and more - Alex Edwards
13.8 parsecs away

Travel
| | [AI summary] The article demonstrates various Go web application techniques including HTTP response handling, templating, and file serving with examples and code snippets.
| | machiel.me
Pongo with Echo or net/http · Machiel
11.6 parsecs away

Travel
| | Freelance developer from Amsterdam, passionate about Go
| | blog.owulveryck.info
IaaS-like RESTfull API based on microservices - Unladen swallow - Olivier Wulveryck
31.5 parsecs away

Travel
| Abstracts Recently, I've been looking at the principles of a middleware layer and especially on how a RESTFULL API could glue different IT services together. I am reading more and more about the "API economy" I've also seen this excellent video made by Mat Ryer about how to code an API in GO and why go would be the perfect language to code such a portal. The problem I'm facing is that in the organization I'm working for, the developments are heterogeneous and therefore you can find ruby teams as well as python teams and myself as a go team (That will change in the future anyway) The key point is that I would like my middleware to serve as an entry point to the services provided by the department.