11–20 of 21 posts
mmm, not sure if doing this counts as using 77 lines of code: import ( "github.com/gin-gonic/gin" "github.com/gorilla/websocket" "github.com/olahol/melody" "net/http" "sync" ) But still impressive.
import (
github.com/olahol/melody-jsnes
)Earlier quoted context omitted.
Also the NES emulation is done in Javascript, making the 77 lines a little less impressive. It's "just" server for handling multiplayer part.
Indeed, the title is a bit misleading.
What's the best solution in Go to support graceful degradation for browsers without websockets / networks that disallow it?
I don't get the difference between github.com/gorilla/websocket & github.com/olahol/melody. Does someone have a clue ?
* Clear and easy interface similar to net/http or Gin with event handlers.
* A simple way to broadcast to all or selected connected sessions.
* Message buffers making concurrent writing safe.
* Automatic handling of ping/pong and session timeouts.
It would be nice to see state-synchronization using rewinding like GGPO, instead of just sending the inputs which introduces a lot of latency.
Although it would be a cool thing to make a production ready web hosted multiplayer NES.
Is there any documentation around? I have no idea how any of this code works, and it doesn't seem to similar to the web apps that I have seen before. Haven't worked with melody before either...
The server works by using HTML5 Websockets ( https://developer.mozilla.org/en-US/docs/WebSockets ) which allows browsers to do full duplex communication with the servers (they can push and receive messages without having to poll). The implementation of the multiplayer itself is very simple and consists of these steps: * Pair up players using a map from one session to another. * Start an instance of https://github.com…
Is there any documentation around? I have no idea how any of this code works, and it doesn't seem to similar to the web apps that I have seen before. Haven't worked with melody before either...
The server works by using HTML5 Websockets ( https://developer.mozilla.org/en-US/docs/WebSockets ) which allows browsers to do full duplex communication with the servers (they can push and receive messages without having to poll). The implementation of the multiplayer itself is very simple and consists of these steps: * Pair up players using a map from one session to another. * Start an instance of https://github.com…