/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

 golangbot.com
Implement a WebSocket server in Go (Golang) | golangbot.com
| | www.markusdosch.com
A short historic overview: Building JavaScript apps that receive server events in real-time | Markus Dosch
5.3 parsecs away

Travel
| | When building web apps like chats and multiplayer games, you need to receive events from the server. In the past, such "server push" has been quite difficult to implement. I am going to give an overview on techniques that were used, and how WebSockets make everything better.
| | scorpil.com
The Long Road to HTTP/3 ยท Scorpil
4.7 parsecs away

Travel
| | Short history of HTTP protocol
| | lenholgate.com
WebSockets is a stream, not a message based protocol... - Rambling Comments - Len Holgate's blog
5.0 parsecs away

Travel
| | [AI summary] The author critiques the design of the WebSockets protocol, arguing that despite its claim to be message-based, its fragmentation features effectively turn it into a stream-based protocol that forces manual buffering and complicates application layer design.
| | williamdurand.fr
REST APIs with Symfony2: The Right Way | William Durand
28.4 parsecs away

Travel
| Designing a REST API is not easy. No, really! If you want to design an API the right way, you have to think a lot about everything, and either to be pragmatic or to be an API terrorist. It's not just about GET, POST, PUT, and DELETE. In real life, you have relations between resources, the need to move a resource somewhere else (think about a tree), or you may want to set a specific value to a resource.