diff options
author | marvin-borner@live.com | 2018-04-16 21:09:05 +0200 |
---|---|---|
committer | marvin-borner@live.com | 2018-04-16 21:09:05 +0200 |
commit | cf14306c2b3f82a81f8d56669a71633b4d4b5fce (patch) | |
tree | 86700651aa180026e89a66064b0364b1e4346f3f /assets/php/vendor/react/stream/src/DuplexStreamInterface.php | |
parent | 619b01b3615458c4ed78bfaeabb6b1a47cc8ad8b (diff) |
Main merge to user management system - files are now at /main/public/
Diffstat (limited to 'assets/php/vendor/react/stream/src/DuplexStreamInterface.php')
-rwxr-xr-x | assets/php/vendor/react/stream/src/DuplexStreamInterface.php | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/assets/php/vendor/react/stream/src/DuplexStreamInterface.php b/assets/php/vendor/react/stream/src/DuplexStreamInterface.php deleted file mode 100755 index 631ce31..0000000 --- a/assets/php/vendor/react/stream/src/DuplexStreamInterface.php +++ /dev/null @@ -1,39 +0,0 @@ -<?php - -namespace React\Stream; - -/** - * The `DuplexStreamInterface` is responsible for providing an interface for - * duplex streams (both readable and writable). - * - * It builds on top of the existing interfaces for readable and writable streams - * and follows the exact same method and event semantics. - * If you're new to this concept, you should look into the - * `ReadableStreamInterface` and `WritableStreamInterface` first. - * - * Besides defining a few methods, this interface also implements the - * `EventEmitterInterface` which allows you to react to the same events defined - * on the `ReadbleStreamInterface` and `WritableStreamInterface`. - * - * The event callback functions MUST be a valid `callable` that obeys strict - * parameter definitions and MUST accept event parameters exactly as documented. - * The event callback functions MUST NOT throw an `Exception`. - * The return value of the event callback functions will be ignored and has no - * effect, so for performance reasons you're recommended to not return any - * excessive data structures. - * - * Every implementation of this interface MUST follow these event semantics in - * order to be considered a well-behaving stream. - * - * > Note that higher-level implementations of this interface may choose to - * define additional events with dedicated semantics not defined as part of - * this low-level stream specification. Conformance with these event semantics - * is out of scope for this interface, so you may also have to refer to the - * documentation of such a higher-level implementation. - * - * @see ReadableStreamInterface - * @see WritableStreamInterface - */ -interface DuplexStreamInterface extends ReadableStreamInterface, WritableStreamInterface -{ -} |