https://github.com/async-interop/event-loop

An event loop interface for interoperability in PHP.
https://github.com/async-interop/event-loop

asynchronous event-loop interoperability php

Last synced: 3 months ago
JSON representation

An event loop interface for interoperability in PHP.

• Host: GitHub
• URL: https://github.com/async-interop/event-loop
• Owner: async-interop
• License: mit
• Created: 2016-01-20T10:52:37.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2017-03-19T07:53:36.000Z (over 7 years ago)
• Last Synced: 2024-03-16T07:21:01.306Z (3 months ago)
• Topics: asynchronous, event-loop, interoperability, php
• Language: PHP
• Homepage:
• Size: 133 KB
• Stars: 169
• Watchers: 28
• Forks: 10
• Open Issues: 12
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• awesome-stars - async-interop/event-loop - An event loop interface for interoperability in PHP. (PHP)

README

        
# Event Loop Interopability

The purpose of this specification is to provide a common interface for

event loop implementations. This allows libraries and components from

different vendors to operate in an event driven architecture, sharing a

common event loop.

## Current Status

This project is currently on hold and to be seen as failed for now. It might be reconsidered at a later point in time. The specification in its current state has been merged into [Amp](https://github.com/amphp/amp). Interoperability between [ReactPHP](https://github.com/reactphp/event-loop) and Amp will be solved via adapters instead of a common interface. [Icicle](https://github.com/icicleio/icicle) has been deprecated and parts of it been merged into Amp libraries.

## Why Bother?

Some programming languages, such as Javascript, have an event loop that is

native to the execution environment. This allows package vendors to easily

create asynchronous software that uses this native event loop. Although PHP

is historically a synchronous programming environment, it is still possible

to use asynchronous programming techniques. Using these techniques, package

vendors have created event loop implementations that have seen success.

However, as these event loop implementations are from package vendors, it

is not yet possible to create event driven software components that are

independent of the underlying event loop implementation. By creating a

common interface for an event loop, interoperability of this nature will

be possible.

## Goals

The functionality exposed by this interface should include the ability to:

- Watch input streams for available data

- Watch output streams for the ability to perform non-blocking write operations

- Run single and periodic timers

- Listen for signals

- Defer the execution of callables

## Implementations

You can find [available implementations on Packagist](https://packagist.org/providers/async-interop/event-loop-implementation).

## Compatible Packages

You can find [compatible packages on Packagist](https://packagist.org/packages/async-interop/event-loop/dependents).

## Contributors

* [Aaron Piotrowski](https://github.com/trowski)

* [Andrew Carter](https://github.com/AndrewCarterUK)

* [Bob Weinand](https://github.com/bwoebi)

* [Cees-Jan Kiewiet](https://github.com/WyriHaximus)

* [Christopher Pitt](https://github.com/assertchris)

* [Daniel Lowrey](https://github.com/rdlowrey)

* [Niklas Keller](https://github.com/kelunik)

* [Stephen M. Coakley](https://github.com/coderstephen)