Projects tagged ‘asynchronous’ and ‘event’


Jump to tag:

Projects tagged ‘asynchronous’ and ‘event’

Filtered by Project Tags asynchronous event

Refine results Project Tags async (6) python (6) server (4) libevent (4) wsgi (4) http (3) socket (3) event-driven (2) fapws (2) django (2) c (2) epoll (2)

[13 total ]

9 Users

The Netty project is an effort to provide an asynchronous event-driven network application framework and tools for rapid development of maintainable high performance and high scalability protocol ... [More] servers and clients. In other words, Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server. [Less]
Created about 1 year ago.

1 Users

gevent is a coroutine-based Python networking library that uses greenlet to provide a high-level synchronous API on top of libevent event loop. Features include: convenient API around ... [More] greenlets familiar synchronization primitives socket module that cooperates WSGI server on top of libevent-http DNS requests done through libevent-dns monkey patching utility to get pure Python modules to cooperate [Less]
Created 4 months ago.

0 Users

Async FutureAn API extension Java Futures and Non-Blocking + Asynchronous I/O and possibly other use-cases (see below). IntroductionThe first sentence of the Java API Doc for Futures says: A Future ... [More] represents the result of an asynchronous computation. In reality it's the result of an asynchronously scheduled or executed computation while the computation itself is a synchronous process. The process is represented by a Runnable or Callable object. Each computation is utilizing at least one Thread throughout its life-time and the Thread is being released when the run() or call() methods return. The problem with this system is that it does not scale very well if the computations are non-deterministic in terms of the time they need to complete and it is also wasting resources if the computations are being performed in a distributed environment (i.e. on a remote machine). AsyncFutures extend the concept of Futures by three simple features to solve these problems. Timeouts Callbacks Asynchronous Processes Timeouts ensure that all computations are deterministic in terms of the time they need to complete. Callbacks enable the user to receive completion events instead of having to wait for the Futures to complete and Asynchronous Processes allow the user to start a computation and let an another Thread (like a NIO Network Thread) return the result. NetworkingTo be written but see Examples for a little example with HttpCore 4.0.1 and NIO. OtherTo be written [Less]
Created about 1 month ago.

0 Users

It's let you very easily to build async socket application. it solves socket's complete events,error handling,IO buffer for package receive and visio packet、pack、unpack...... all you need to do is implement two interface
Created 3 months ago.

0 Users

Library to add event support to APR.
Created 3 months ago.

0 Users

YPy is a Yield-based Python application server that uses Stackless Python/the greenlets module for transparent stack switching in Python. YPy is not a web framework, but a web server like Apache with ... [More] mod_python/mod_wsgi for Python or Mongrel for Ruby on Rails. YPy is primarily intended as a WSGI server, though it can be used for other (non-web) applications. See the YPy README.txt for instructions on installing YPy. See BasicWSGIServer for instructions on how to get a basic WSGI application running under YPy. [Less]
Created 8 months ago.

0 Users

More and more applications are coming to rely on pyevent. The problem is that pyevent itself requires compiling external modules and therefore presents a deployment hurdle. The rel module is a drop-in ... [More] replacement for pyevent that completely emulates pyevent's interface, behavior and functionality on any system with Python. It will use pyevent if it's available, and if it's not rel will use the fastest method supported by the system. Epoll, poll, and select are currently implemented. To use rel: download it: 'sudo easy_install rel' or install the package hosted here. put 'import rel; rel.override()' at the top of the start script for your pyevent application [Less]
Created 12 months ago.

0 Users

EvServer is a lightweight http server, created especially to host python WSGI applications. Additionally, it supports little known Asynchronous WSGI extension, which was suggested by Christopher ... [More] Stawarz. Using this extension it's possible to create an output html response in many data chunks, without blocking the main server process while your application waits for external resources. EvServer is created on top of the battle tested libevent library. It should be bleeding fast and reasonably stable. The long term goal for this project, is to create a tool that will allow to easily create scalable comet/http push web applications. This server allows you to use comet in your WSGI applications. [Less]
Created 12 months ago.

0 Users

Python WSGI HTTP server on libev.
Created 5 months ago.

0 Users

Boost.Join is an asynchronous, message based C++ concurrency library based on Join calculus. It is applicable both to multi-threaded applications and to the orchestration of asynchronous, event-based ... [More] applications. It follows Comega's design and implementation and builds with Boost facilities. It provides a high level concurrency API with asynchronous methods, synchronous methods, and chords which are 'join-patterns' defining the synchronization, asynchrony, and concurrency. More info is available at http://channel.sourceforge.net [Less]
Created 12 months ago.