Search Results for "linux socket thread"

SMUX is a stream multiplexing library for Go that lets multiple logical streams share one reliable underlying connection. It is designed for transports such as TCP or KCP, where ordering and reliability are already provided by the lower layer. The library uses sessions, streams, and frames to manage many independent data flows over a single connection. It focuses on controlled memory usage, smooth receiving behavior, fair traffic shaping, and small protocol overhead. Its design includes a...

go-socket.io is the library implementation of Socket.IO in Golang, which is a real-time application framework. Current this library supports 1.4 version of the Socket.IO client. It supports room, namespaces and broadcast at now. This project is looking for contributors to help fix bugs and implement new features.

Gev is a lightweight, fast non-blocking TCP network library / websocket server based on Reactor mode. Support custom protocols to quickly and easily build high-performance servers. Support custom protocols to quickly and easily build high-performance servers. High-performance event loop based on epoll and kqueue. Support multi-core and multi-threading. Dynamic expansion of read and write buffers implemented by Ring Buffer. Asynchronous read and write. SO_REUSEPORT port reuse support....

cache2go is an in-memory caching library for Go that provides a simple and efficient way to store and retrieve data with optional expiration policies. It supports multiple independent cache tables, allowing developers to organize cached data according to different use cases or domains. The library includes features such as automatic expiration, callbacks on data eviction, and thread-safe operations for concurrent environments. It is designed to be easy to integrate into Go applications,...

go-cache is an in-memory key:value store/cache similar to memcached that is suitable for applications running on a single machine. Its major advantage is that, being essentially a thread-safe map[string]interface{} with expiration times, it doesn't need to serialize or transmit its contents over the network. Any object can be stored, for a given duration or forever, and the cache can be safely used by multiple goroutines. Although go-cache isn't meant to be used as a persistent datastore,...