Displaying 1 to 7 from 7 results

swoole-src - Event-driven asynchronous & concurrent & coroutine networking engine with high performance for PHP

  •    C

Swoole is an event-driven asynchronous & concurrent networking communication framework with high performance written only in C for PHP.The network layer in Swoole is event-based and takes full advantage of the underlaying epoll/kqueue implementation, making it really easy to serve thousands of connections.

libae - redis's async event loop library

  •    C

Redis's async event library, you can use it in your projects.

aioice - asyncio-based Interactive Connectivity Establishment (RFC 5245)

  •    Python

aioice is a library for Interactive Connectivity Establishment (RFC 5245) in Python. It is built on top of asyncio, Python's standard asynchronous I/O framework. Interactive Connectivity Establishment (ICE) is useful for applications that establish peer-to-peer UDP data streams, as it facilitates NAT traversal. Typical usecases include SIP and WebRTC.

NLibuv - Libuv bindings for .NET

  •    CSharp

A cross-platform bindings to the libuv library for .NET. The purpose of this library is to provide the libuv API on .NET platform, as simple as possible. It requires you to write your code as if you were using libuv directly. NLibuv takes care of platform invoke, marshaling, error handling and memory management, allowing you to consume libuv API as it is, safely on any platform supported by .NET.

vibe-core - Repository for the next generation of vibe.d's core package.

  •    D

The fundamental building block is the fiber based task concept, together with the event based asynchronous I/O model. This enables developing highly scalable I/O concurrent applications without running into the complexities and design implications that asynchronous I/O programming models usually impose. See the features page for a more detailed explanation. This is the successor of the vibe-d:core sub package of vibe.d 0.7.x. The API is mostly compatible from a library user point of view, but the whole library has received some heavy lifting under the surface, close to a rewrite. Most classes have been replaced by reference counting structs and @safe nothrow attributes are now used throughout the library, whenever possible. Adding @nogc on the other hand could only be done in a very limited context due to its viral nature and the lack of an @trusted equivalent.