A Go websocket library with an API similar to Socket.IO... but not Socket.IO
Go to file
2018-10-17 20:12:26 -07:00
backend just a fmt 2018-05-17 19:55:13 -07:00
client Merge branch 'master' of https://github.com/raz-varren/sacrificial-socket 2018-04-15 13:19:32 -07:00
examples added socketcast 2018-10-17 20:12:26 -07:00
vendor added socketcast 2018-10-17 20:12:26 -07:00
.gitignore added vendor 2018-05-17 20:09:33 -07:00
hub.go let there be websockets 2016-08-09 00:48:14 +00:00
LICENSE moved log into it's own repository 2018-03-20 21:07:20 +00:00
README.md removed deprecated SocketServer.WebHandler() method from examples 2018-04-15 13:27:22 -07:00
rng.go fix rng documentation 2018-05-18 12:10:48 -07:00
server_test.go missed one 2018-04-15 13:35:56 -07:00
server.go added socketcast 2018-10-17 20:12:26 -07:00
socket.go added socketcast 2018-10-17 20:12:26 -07:00

Sacrificial-Socket GoDoc

A Go server library and pure JS client library for managing communication between websockets, that has an API similar to Socket.IO, but feels less... well, Javascripty. Socket.IO is great, but nowadays all modern browsers support websockets natively, so in most cases there is no need to have websocket simulation fallbacks like XHR long polling or Flash. Removing these allows Sacrificial-Socket to be lightweight and very performant.

Sacrificial-Socket supports rooms, roomcasts, broadcasts, and event emitting just like Socket.IO, but with one key difference. The data passed into event functions is not an interface{} that is implied to be a string or map[string]interface{}, but is always passed in as a []byte making it easier to unmarshal into your own JSON data structs, convert to a string, or keep as binary data without the need to check the data's type before processing it. It also means there aren't any unnecessary conversions to the data between the client and the server.

Sacrificial-Socket also has a MultihomeBackend interface for syncronizing broadcasts and roomcasts across multiple instances of Sacrificial-Socket running on multiple machines. Out of the box Sacrificial-Socket provides a MultihomeBackend interface for the popular noSQL database MongoDB, one for the moderately popular key/value storage engine Redis, and one for the not so popular GRPC protocol, for syncronizing instances on multiple machines.

In depth examples can be found in the examples directory.

Usage

Client Javascript:

(function(SS){ 'use strict';
    var ss = new SS('ws://localhost:8080/socket');
    ss.onConnect(function(){
        ss.emit('echo', 'hello echo!');
    });
    
    ss.on('echo', function(data){
        alert('got echo:', data);
        ss.close();
    });
    
    ss.onDisconnect(function(){
        console.log('socket connection closed');
    });
})(window.SS);

Server Go:

package main

import(
    "net/http"
    ss "github.com/raz-varren/sacrificial-socket"
)

func doEcho(s *ss.Socket, data []byte) {
    s.Emit("echo", string(data))
}

func main() {
    s := ss.NewServer()
    s.On("echo", doEcho)
    
    http.Handle("/socket", s)
    http.ListenAndServe(":8080", nil);
}