Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.15.147.225
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
unp_probe /
vendor /
react /
stream /
src /
Delete
Unzip
Name
Size
Permission
Date
Action
CompositeStream.php
1.83
KB
-rw-r--r--
2020-05-04 10:17
DuplexResourceStream.php
6.64
KB
-rw-r--r--
2020-05-04 10:17
DuplexStreamInterface.php
1.68
KB
-rw-r--r--
2020-05-04 10:17
ReadableResourceStream.php
5.58
KB
-rw-r--r--
2020-05-04 10:17
ReadableStreamInterface.php
13.9
KB
-rw-r--r--
2020-05-04 10:17
ThroughStream.php
4.81
KB
-rw-r--r--
2020-05-04 10:17
Util.php
2.23
KB
-rw-r--r--
2020-05-04 10:17
WritableResourceStream.php
4.98
KB
-rw-r--r--
2020-05-04 10:17
WritableStreamInterface.php
14.4
KB
-rw-r--r--
2020-05-04 10:17
Save
Rename
<?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 { }