Search Results for "interface"

webrpc is a schema-driven approach to writing backend servers for the Web. Write your server's API interface in a schema format of RIDL or JSON, and then run webrpc-gen to generate the networking source code for your server and client apps. From the schema, webrpc-gen will generate application-based class types/interfaces, JSON encoders, and networking code. In doing so, it's able to generate fully functioning and typed client libraries to communicate with your server.

Getty is an asynchronous network I/O library developed in Golang. It operates on TCP, UDP, and WebSocket network protocols, providing a consistent interface EventListener. Within Getty, each connection (session) involves two separate goroutines. One handles the reading of TCP streams, UDP packets, or WebSocket packages, while the other manages the logic processing and writes responses into the network write buffer. If your logic processing might take a considerable amount of time, it's recommended to start a new logic process goroutine yourself within codec.go's (Codec)OnMessage method. ...

...However, Badger is not suitable for every scenario (for example, when the database size is a constraint). This is why, the storage layer of CloverDB has been abstracted through a set of interface types to work with any key-value store. At the moment, CloverDB can work with both Badger and Bolt (by default Bolt is used).

DJSON is a JSON decoder for Go that is 2~ to 3~ times faster than the standard encoding/json and the existing solutions when dealing with arbitrary JSON payload. It is a good approach for people who are using json.Unmarshal together with interface, don't know what the schema is, and still want good performance with minimal changes. DJSON is faster and allocates less memory than the other alternatives.