/explore
|
You are here 
|
www.alexedwards.net | ||
| | | | |
aarol.dev
|
|
| | | | | Anyone who has implemented a simple HTTP 1.1 server can tell you that it is a really simple protocol. Basically, it's a text file that has some specific ... | |
| | | | |
xnacly.me
|
|
| | | | | Guide about working with JSON in go with HTTP server example | |
| | | | |
hjr265.me
|
|
| | | | | I know many will start with something like Gin whenever they are working on a JSON/HTTP-based backend in Go. I, not entirely sure if the minority, try to stick to Go's built-in net/http package and, at most, use Gorilla Mux in most of my Go projects. And so serving something simple like JSON is no different from the package's point of view as any other content type: whatever it is, write it out to the w, the http. | |
| | | | |
limpet.net
|
|
| | | [AI summary] This article explains Rust's memory safety guarantees by reframing the compiler's borrowing and lifetime checks as a system of unique versus shared access to data. | ||
