Explore >> Select a destination
|
You are here 
|
hypirion.com | ||
| | | | |
matttproud.com
|
|
| | | | | I would like to propose a set of neologisms for the Go Programming Language based on emergent language use: context awareness: noun, the state of an API being cognizant of and respecting the semantics of the context API. Example: Function f has context awareness. context-aware or1 context aware: phrasal adjective, whether an API has context awareness. Examples: The API consumes a context-aware function value like function f. Function f is context aware. | |
| | | | |
pauladamsmith.com
|
|
| | | | | This is a simple and easily generalizable way to put an upper-bound on the maximum number of simultaneous clients to a Go net/http server or handler. The idea is to use a counting semaphore, modeled with a buffered channel, to cause new clients to... | |
| | | | |
jbrandhorst.com
|
|
| | | | | Sometimes when you're writing a server, you've got a function that consumes a lot of memory while running, or some other resource, and you might be worrying that a sudden burst of requests could crash the server, since gRPC by default will just spawn another goroutine to handle any incoming requests, oblivious to the danger. In these situations, it can be useful to implement some custom request throttling. Here I'll show an easy way to accomplish this with the use of a Go channel. | |
| | | | |
rakhim.org
|
|
| | | |||
