Explore >> Select a destination
|
You are here 
|
ekhabarov.com | ||
| | | | |
mfbmina.dev
|
|
| | | | | The first time I heard about RPC, I was in a distributed systems class while completing my bachelor's in computer science. I like it but didn't fully understand why I should use it instead of REST. Time passed, and I started working at a company where the legacy services use SOAP. I remember thinking: "hm, that's cool! It is like RPC but using XML instead! Years later, I heard for the first time about gRPC, but I've never fully understood it until now! | |
| | | | |
ectobit.com
|
|
| | | | | Differences between APIv1 and APIv2 implementation of protocol buffers and gRPC in Golang | |
| | | | |
blog.owulveryck.info
|
|
| | | | | This is a simple article that describes the wiring of the tool I made for streaming the content of the remarkable 2 on a computer. From the proc filesystem to the gRPC implementation over HTTP/2 via the certificate generation. | |
| | | | |
www.integralist.co.uk
|
|
| | | The following code doesn't do what you might expect: package main import "fmt" func main() { var i *impl fmt.Println("i == nil:", i == nil) what(i) } type impl struct{} func (i *impl) do() {} func what(i interface{ do() }) { fmt.Println("i == nil:", i == nil) } If you expected the what function to print i == nil: true, then keep reading... Typed Nils The behavior observed is due to the way interfaces and nil values interact in Go. | ||
