Download the PHP package clue/block-react without Composer

Deprecation notice

This package has now been migrated over to reactphp/async and only exists for BC reasons.

Only the await() function has been merged without its optional parameters $loop and $timeout, the rest of await() works as-is from the latest v1.5.0 release with no other significant changes. Simply update your code to use the updated namespace like this:

See reactphp/async for more details.

The below documentation applies to the last release of this package. Further development will take place in the updated reactphp/async, so you're highly recommended to upgrade as soon as possible.

Legacy clue/reactphp-block

Lightweight library that eases integrating async components built for ReactPHP in a traditional, blocking environment.

ReactPHP provides you a great set of base components and a huge ecosystem of third party libraries in order to perform async operations. The event-driven paradigm and asynchronous processing of any number of streams in real time enables you to build a whole new set of application on top of it. This is great for building modern, scalable applications from scratch and will likely result in you relying on a whole new software architecture.

But let's face it: Your day-to-day business is unlikely to allow you to build everything from scratch and ditch your existing production environment. This is where this library comes into play:

Let's block ReactPHP More specifically, this library eases the pain of integrating async components into your traditional, synchronous (blocking) application stack.

Table of contents

• Support us
• Quickstart example
• Usage
  • sleep()
  • await()
  • awaitAny()
  • awaitAll()
• Install
• Tests
• License

Support us

We invest a lot of time developing, maintaining and updating our awesome open-source projects. You can help us sustain this high-quality of our work by becoming a sponsor on GitHub. Sponsors get numerous benefits in return, see our sponsoring page for details.

Let's take these projects to the next level together! 🚀

Quickstart example

The following example code demonstrates how this library can be used along with an async HTTP client to process two non-blocking HTTP requests and block until the first (faster) one resolves.

Usage

This lightweight library consists only of a few simple functions. All functions reside under the Clue\React\Block namespace.

The below examples refer to all functions with their fully-qualified names like this:

As of PHP 5.6+ you can also import each required function into your code like this:

Alternatively, you can also use an import statement similar to this:

sleep()

The sleep(float $seconds, ?LoopInterface $loop = null): void function can be used to wait/sleep for $time seconds.

This function will only return after the given $time has elapsed. In the meantime, the event loop will run any other events attached to the same loop until the timer fires. If there are no other events attached to this loop, it will behave similar to the built-in sleep().

Internally, the $time argument will be used as a timer for the loop so that it keeps running until this timer triggers. This implies that if you pass a really small (or negative) value, it will still start a timer and will thus trigger at the earliest possible time in the future.

This function takes an optional LoopInterface|null $loop parameter that can be used to pass the event loop instance to use. You can use a null value here in order to use the default loop. This value SHOULD NOT be given unless you're sure you want to explicitly use a given event loop instance.

Note that this function will assume control over the event loop. Internally, it will actually run() the loop until the timer fires and then calls stop() to terminate execution of the loop. This means this function is more suited for short-lived program executions when using async APIs is not feasible. For long-running applications, using event-driven APIs by leveraging timers is usually preferable.

await()

The await(PromiseInterface $promise, ?LoopInterface $loop = null, ?float $timeout = null): mixed function can be used to block waiting for the given $promise to be fulfilled.

This function will only return after the given $promise has settled, i.e. either fulfilled or rejected. In the meantime, the event loop will run any events attached to the same loop until the promise settles.

Once the promise is fulfilled, this function will return whatever the promise resolved to.

Once the promise is rejected, this will throw whatever the promise rejected with. If the promise did not reject with an Exception, then this function will throw an UnexpectedValueException instead.

See also the examples.

This function takes an optional LoopInterface|null $loop parameter that can be used to pass the event loop instance to use. You can use a null value here in order to use the default loop. This value SHOULD NOT be given unless you're sure you want to explicitly use a given event loop instance.

If no $timeout argument is given and the promise stays pending, then this will potentially wait/block forever until the promise is settled. To avoid this, API authors creating promises are expected to provide means to configure a timeout for the promise instead. For more details, see also the timeout() function.

If the deprecated $timeout argument is given and the promise is still pending once the timeout triggers, this will cancel() the promise and throw a TimeoutException. This implies that if you pass a really small (or negative) value, it will still start a timer and will thus trigger at the earliest possible time in the future.

Note that this function will assume control over the event loop. Internally, it will actually run() the loop until the promise settles and then calls stop() to terminate execution of the loop. This means this function is more suited for short-lived promise executions when using promise-based APIs is not feasible. For long-running applications, using promise-based APIs by leveraging chained then() calls is usually preferable.

awaitAny()

The awaitAny(PromiseInterface[] $promises, ?LoopInterface $loop = null, ?float $timeout = null): mixed function can be used to wait for ANY of the given promises to be fulfilled.

See also the examples.

This function will only return after ANY of the given $promises has been fulfilled or will throw when ALL of them have been rejected. In the meantime, the event loop will run any events attached to the same loop.

Once ANY promise is fulfilled, this function will return whatever this promise resolved to and will try to cancel() all remaining promises.

Once ALL promises reject, this function will fail and throw an UnderflowException. Likewise, this will throw if an empty array of $promises is passed.

This function takes an optional LoopInterface|null $loop parameter that can be used to pass the event loop instance to use. You can use a null value here in order to use the default loop. This value SHOULD NOT be given unless you're sure you want to explicitly use a given event loop instance.

If no $timeout argument is given and ALL promises stay pending, then this will potentially wait/block forever until the promise is fulfilled. To avoid this, API authors creating promises are expected to provide means to configure a timeout for the promise instead. For more details, see also the timeout() function.

If the deprecated $timeout argument is given and ANY promises are still pending once the timeout triggers, this will cancel() all pending promises and throw a TimeoutException. This implies that if you pass a really small (or negative) value, it will still start a timer and will thus trigger at the earliest possible time in the future.

Note that this function will assume control over the event loop. Internally, it will actually run() the loop until the promise settles and then calls stop() to terminate execution of the loop. This means this function is more suited for short-lived promise executions when using promise-based APIs is not feasible. For long-running applications, using promise-based APIs by leveraging chained then() calls is usually preferable.

awaitAll()

The awaitAll(PromiseInterface[] $promises, ?LoopInterface $loop = null, ?float $timeout = null): mixed[] function can be used to wait for ALL of the given promises to be fulfilled.

See also the examples.

This function will only return after ALL of the given $promises have been fulfilled or will throw when ANY of them have been rejected. In the meantime, the event loop will run any events attached to the same loop.

Once ALL promises are fulfilled, this will return an array with whatever each promise resolves to. Array keys will be left intact, i.e. they can be used to correlate the return array to the promises passed. Likewise, this will return an empty array if an empty array of $promises is passed.

Once ANY promise rejects, this will try to cancel() all remaining promises and throw an Exception. If the promise did not reject with an Exception, then this function will throw an UnexpectedValueException instead.

This function takes an optional LoopInterface|null $loop parameter that can be used to pass the event loop instance to use. You can use a null value here in order to use the default loop. This value SHOULD NOT be given unless you're sure you want to explicitly use a given event loop instance.

If no $timeout argument is given and ANY promises stay pending, then this will potentially wait/block forever until the promise is fulfilled. To avoid this, API authors creating promises are expected to provide means to configure a timeout for the promise instead. For more details, see also the timeout() function.

If the deprecated $timeout argument is given and ANY promises are still pending once the timeout triggers, this will cancel() all pending promises and throw a TimeoutException. This implies that if you pass a really small (or negative) value, it will still start a timer and will thus trigger at the earliest possible time in the future.

Note that this function will assume control over the event loop. Internally, it will actually run() the loop until the promise settles and then calls stop() to terminate execution of the loop. This means this function is more suited for short-lived promise executions when using promise-based APIs is not feasible. For long-running applications, using promise-based APIs by leveraging chained then() calls is usually preferable.

Install

The recommended way to install this library is through Composer. New to Composer?

This project follows SemVer. This will install the latest supported version:

See also the CHANGELOG for details about version upgrades.

This project aims to run on any platform and thus does not require any PHP extensions and supports running on legacy PHP 5.3 through current PHP 8+ and HHVM. It's highly recommended to use the latest supported PHP version for this project.

Tests

To run the test suite, you first need to clone this repo and then install all dependencies through Composer:

To run the test suite, go to the project root and run:

License

This project is released under the permissive MIT license.

Did you know that I offer custom development services and issuing invoices for sponsorships of releases and for contributions? Contact me (@clue) for details.