Maintenance Mode
This component has now been merged into the
Socket component and only exists for BC
reasons., (*1)
$ composer require react/socket
If you've previously used the SocketClient component to establish outgoing
client connections, upgrading should take no longer than a few minutes.
All classes have been merged as-is from the latest v0.7.0 release with no
other changes, so you can simply update your code to use the updated namespace
like this:, (*2)
// old from SocketClient component and namespace
$connector = new React\SocketClient\Connector($loop);
$connector->connect('google.com:80')->then(function (ConnectionInterface $conn) {
$connection->write('…');
});
// new
$connector = new React\Socket\Connector($loop);
$connector->connect('google.com:80')->then(function (ConnectionInterface $conn) {
$connection->write('…');
});
See https://github.com/reactphp/socket for more details., (*3)
The below documentation applies to the last release of this component.
Further development will take place in the updated
Socket component, so you're highly
recommended to upgrade as soon as possible., (*4)
Legacy SocketClient Component
, (*5)
Async, streaming plaintext TCP/IP and secure TLS based connections for ReactPHP, (*6)
You can think of this library as an async version of
fsockopen() or
stream_socket_client().
If you want to transmit and receive data to/from a remote server, you first
have to establish a connection to the remote end.
Establishing this connection through the internet/network may take some time
as it requires several steps (such as resolving target hostname, completing
TCP/IP handshake and enabling TLS) in order to complete.
This component provides an async version of all this so you can establish and
handle multiple connections without blocking., (*7)
Table of Contents, (*8)
Usage
ConnectorInterface
The ConnectorInterface is responsible for providing an interface for
establishing streaming connections, such as a normal TCP/IP connection., (*9)
This is the main interface defined in this package and it is used throughout
React's vast ecosystem., (*10)
Most higher-level components (such as HTTP, database or other networking
service clients) accept an instance implementing this interface to create their
TCP/IP connection to the underlying networking service.
This is usually done via dependency injection, so it's fairly simple to actually
swap this implementation against any other implementation of this interface., (*11)
The interface only offers a single method:, (*12)
connect()
The connect(string $uri): PromiseInterface<ConnectionInterface, Exception> method
can be used to create a streaming connection to the given remote address., (*13)
It returns a Promise which either
fulfills with a stream implementing ConnectionInterface
on success or rejects with an Exception if the connection is not successful:, (*14)
$connector->connect('google.com:443')->then(
function (ConnectionInterface $connection) {
// connection successfully established
},
function (Exception $error) {
// failed to connect due to $error
}
);
See also ConnectionInterface for more details., (*15)
The returned Promise MUST be implemented in such a way that it can be
cancelled when it is still pending. Cancelling a pending promise MUST
reject its value with an Exception. It SHOULD clean up any underlying
resources and references as applicable:, (*16)
$promise = $connector->connect($uri);
$promise->cancel();
ConnectionInterface
The ConnectionInterface is used to represent any outgoing connection,
such as a normal TCP/IP connection., (*17)
An outgoing connection is a duplex stream (both readable and writable) that
implements React's
DuplexStreamInterface.
It contains additional properties for the local and remote address
where this connection has been established to., (*18)
Most commonly, instances implementing this ConnectionInterface are returned
by all classes implementing the ConnectorInterface., (*19)
Note that this interface is only to be used to represent the client-side end
of an outgoing connection.
It MUST NOT be used to represent an incoming connection in a server-side context.
If you want to accept incoming connections,
use the Socket component instead., (*20)
Because the ConnectionInterface implements the underlying
DuplexStreamInterface
you can use any of its events and methods as usual:, (*21)
$connection->on('data', function ($chunk) {
echo $chunk;
});
$connection->on('end', function () {
echo 'ended';
});
$connection->on('error', function (Exception $e) {
echo 'error: ' . $e->getMessage();
});
$connection->on('close', function () {
echo 'closed';
});
$connection->write($data);
$connection->end($data = null);
$connection->close();
// …
For more details, see the
DuplexStreamInterface., (*22)
getRemoteAddress()
The getRemoteAddress(): ?string method can be used to
return the remote address (IP and port) where this connection has been
established to., (*23)
$address = $connection->getRemoteAddress();
echo 'Connected to ' . $address . PHP_EOL;
If the remote address can not be determined or is unknown at this time (such as
after the connection has been closed), it MAY return a NULL value instead., (*24)
Otherwise, it will return the full remote address as a string value.
If this is a TCP/IP based connection and you only want the remote IP, you may
use something like this:, (*25)
$address = $connection->getRemoteAddress();
$ip = trim(parse_url('tcp://' . $address, PHP_URL_HOST), '[]');
echo 'Connected to ' . $ip . PHP_EOL;
getLocalAddress()
The getLocalAddress(): ?string method can be used to
return the full local address (IP and port) where this connection has been
established from., (*26)
$address = $connection->getLocalAddress();
echo 'Connected via ' . $address . PHP_EOL;
If the local address can not be determined or is unknown at this time (such as
after the connection has been closed), it MAY return a NULL value instead., (*27)
Otherwise, it will return the full local address as a string value., (*28)
This method complements the getRemoteAddress() method,
so they should not be confused., (*29)
If your system has multiple interfaces (e.g. a WAN and a LAN interface),
you can use this method to find out which interface was actually
used for this connection., (*30)
Connector
The Connector class is the main class in this package that implements the
ConnectorInterface and allows you to create streaming connections., (*31)
You can use this connector to create any kind of streaming connections, such
as plaintext TCP/IP, secure TLS or local Unix connection streams., (*32)
It binds to the main event loop and can be used like this:, (*33)
$loop = React\EventLoop\Factory::create();
$connector = new Connector($loop);
$connector->connect($uri)->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
$loop->run();
In order to create a plaintext TCP/IP connection, you can simply pass a host
and port combination like this:, (*34)
$connector->connect('www.google.com:80')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
If you do no specify a URI scheme in the destination URI, it will assume
tcp:// as a default and establish a plaintext TCP/IP connection.
Note that TCP/IP connections require a host and port part in the destination
URI like above, all other URI components are optional., (*35)
In order to create a secure TLS connection, you can use the tls:// URI scheme
like this:, (*36)
$connector->connect('tls://www.google.com:443')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
In order to create a local Unix domain socket connection, you can use the
unix:// URI scheme like this:, (*37)
$connector->connect('unix:///tmp/demo.sock')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
Under the hood, the Connector is implemented as a higher-level facade
for the lower-level connectors implemented in this package. This means it
also shares all of their features and implementation details.
If you want to typehint in your higher-level protocol implementation, you SHOULD
use the generic ConnectorInterface instead., (*38)
In particular, the Connector class uses Google's public DNS server 8.8.8.8
to resolve all hostnames into underlying IP addresses by default.
This implies that it also ignores your hosts file and resolve.conf, which
means you won't be able to connect to localhost and other non-public
hostnames by default.
If you want to use a custom DNS server (such as a local DNS relay), you can set
up the Connector like this:, (*39)
$connector = new Connector($loop, array(
'dns' => '127.0.1.1'
));
$connector->connect('localhost:80')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
If you do not want to use a DNS resolver at all and want to connect to IP
addresses only, you can also set up your Connector like this:, (*40)
$connector = new Connector($loop, array(
'dns' => false
));
$connector->connect('127.0.0.1:80')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
Advanced: If you need a custom DNS Resolver instance, you can also set up
your Connector like this:, (*41)
$dnsResolverFactory = new React\Dns\Resolver\Factory();
$resolver = $dnsResolverFactory->createCached('127.0.1.1', $loop);
$connector = new Connector($loop, array(
'dns' => $resolver
));
$connector->connect('localhost:80')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
By default, the tcp:// and tls:// URI schemes will use timeout value that
repects your default_socket_timeout ini setting (which defaults to 60s).
If you want a custom timeout value, you can simply pass this like this:, (*42)
$connector = new Connector($loop, array(
'timeout' => 10.0
));
Similarly, if you do not want to apply a timeout at all and let the operating
system handle this, you can pass a boolean flag like this:, (*43)
$connector = new Connector($loop, array(
'timeout' => false
));
By default, the Connector supports the tcp://, tls:// and unix://
URI schemes. If you want to explicitly prohibit any of these, you can simply
pass boolean flags like this:, (*44)
// only allow secure TLS connections
$connector = new Connector($loop, array(
'tcp' => false,
'tls' => true,
'unix' => false,
));
$connector->connect('tls://google.com:443')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
The tcp:// and tls:// also accept additional context options passed to
the underlying connectors.
If you want to explicitly pass additional context options, you can simply
pass arrays of context options like this:, (*45)
// allow insecure TLS connections
$connector = new Connector($loop, array(
'tcp' => array(
'bindto' => '192.168.0.1:0'
),
'tls' => array(
'verify_peer' => false,
'verify_peer_name' => false
),
));
$connector->connect('tls://localhost:443')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
For more details about context options, please refer to the PHP documentation
about socket context options
and SSL context options., (*46)
Advanced: By default, the Connector supports the tcp://, tls:// and
unix:// URI schemes.
For this, it sets up the required connector classes automatically.
If you want to explicitly pass custom connectors for any of these, you can simply
pass an instance implementing the ConnectorInterface like this:, (*47)
$dnsResolverFactory = new React\Dns\Resolver\Factory();
$resolver = $dnsResolverFactory->createCached('127.0.1.1', $loop);
$tcp = new DnsConnector(new TcpConnector($loop), $resolver);
$tls = new SecureConnector($tcp, $loop);
$unix = new UnixConnector($loop);
$connector = new Connector($loop, array(
'tcp' => $tcp,
'tls' => $tls,
'unix' => $unix,
'dns' => false,
'timeout' => false,
));
$connector->connect('google.com:80')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
Internally, the tcp:// connector will always be wrapped by the DNS resolver,
unless you disable DNS like in the above example. In this case, the tcp://
connector receives the actual hostname instead of only the resolved IP address
and is thus responsible for performing the lookup.
Internally, the automatically created tls:// connector will always wrap the
underlying tcp:// connector for establishing the underlying plaintext
TCP/IP connection before enabling secure TLS mode. If you want to use a custom
underlying tcp:// connector for secure TLS connections only, you may
explicitly pass a tls:// connector like above instead.
Internally, the tcp:// and tls:// connectors will always be wrapped by
TimeoutConnector, unless you disable timeouts like in the above example., (*48)
Advanced Usage
TcpConnector
The React\SocketClient\TcpConnector class implements the
ConnectorInterface and allows you to create plaintext
TCP/IP connections to any IP-port-combination:, (*49)
$tcpConnector = new React\SocketClient\TcpConnector($loop);
$tcpConnector->connect('127.0.0.1:80')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
$loop->run();
See also the first example., (*50)
Pending connection attempts can be cancelled by cancelling its pending promise like so:, (*51)
$promise = $tcpConnector->connect('127.0.0.1:80');
$promise->cancel();
Calling cancel() on a pending promise will close the underlying socket
resource, thus cancelling the pending TCP/IP connection, and reject the
resulting promise., (*52)
You can optionally pass additional
socket context options
to the constructor like this:, (*53)
$tcpConnector = new React\SocketClient\TcpConnector($loop, array(
'bindto' => '192.168.0.1:0'
));
Note that this class only allows you to connect to IP-port-combinations.
If the given URI is invalid, does not contain a valid IP address and port
or contains any other scheme, it will reject with an
InvalidArgumentException:, (*54)
If the given URI appears to be valid, but connecting to it fails (such as if
the remote host rejects the connection etc.), it will reject with a
RuntimeException., (*55)
If you want to connect to hostname-port-combinations, see also the following chapter., (*56)
Advanced usage: Internally, the TcpConnector allocates an empty context
resource for each stream resource.
If the destination URI contains a hostname query parameter, its value will
be used to set up the TLS peer name.
This is used by the SecureConnector and DnsConnector to verify the peer
name and can also be used if you want a custom TLS peer name., (*57)
DnsConnector
The DnsConnector class implements the
ConnectorInterface and allows you to create plaintext
TCP/IP connections to any hostname-port-combination., (*58)
It does so by decorating a given TcpConnector instance so that it first
looks up the given domain name via DNS (if applicable) and then establishes the
underlying TCP/IP connection to the resolved target IP address., (*59)
Make sure to set up your DNS resolver and underlying TCP connector like this:, (*60)
$dnsResolverFactory = new React\Dns\Resolver\Factory();
$dns = $dnsResolverFactory->createCached('8.8.8.8', $loop);
$dnsConnector = new React\SocketClient\DnsConnector($tcpConnector, $dns);
$dnsConnector->connect('www.google.com:80')->then(function (ConnectionInterface $connection) {
$connection->write('...');
$connection->end();
});
$loop->run();
See also the first example., (*61)
Pending connection attempts can be cancelled by cancelling its pending promise like so:, (*62)
$promise = $dnsConnector->connect('www.google.com:80');
$promise->cancel();
Calling cancel() on a pending promise will cancel the underlying DNS lookup
and/or the underlying TCP/IP connection and reject the resulting promise., (*63)
Advanced usage: Internally, the DnsConnector relies on a Resolver to
look up the IP address for the given hostname.
It will then replace the hostname in the destination URI with this IP and
append a hostname query parameter and pass this updated URI to the underlying
connector.
The underlying connector is thus responsible for creating a connection to the
target IP address, while this query parameter can be used to check the original
hostname and is used by the TcpConnector to set up the TLS peer name.
If a hostname is given explicitly, this query parameter will not be modified,
which can be useful if you want a custom TLS peer name., (*64)
SecureConnector
The SecureConnector class implements the
ConnectorInterface and allows you to create secure
TLS (formerly known as SSL) connections to any hostname-port-combination., (*65)
It does so by decorating a given DnsConnector instance so that it first
creates a plaintext TCP/IP connection and then enables TLS encryption on this
stream., (*66)
$secureConnector = new React\SocketClient\SecureConnector($dnsConnector, $loop);
$secureConnector->connect('www.google.com:443')->then(function (ConnectionInterface $connection) {
$connection->write("GET / HTTP/1.0\r\nHost: www.google.com\r\n\r\n");
...
});
$loop->run();
See also the second example., (*67)
Pending connection attempts can be cancelled by cancelling its pending promise like so:, (*68)
$promise = $secureConnector->connect('www.google.com:443');
$promise->cancel();
Calling cancel() on a pending promise will cancel the underlying TCP/IP
connection and/or the SSL/TLS negonation and reject the resulting promise., (*69)
You can optionally pass additional
SSL context options
to the constructor like this:, (*70)
$secureConnector = new React\SocketClient\SecureConnector($dnsConnector, $loop, array(
'verify_peer' => false,
'verify_peer_name' => false
));
Advanced usage: Internally, the SecureConnector relies on setting up the
required context options on the underlying stream resource.
It should therefor be used with a TcpConnector somewhere in the connector
stack so that it can allocate an empty context resource for each stream
resource and verify the peer name.
Failing to do so may result in a TLS peer name mismatch error or some hard to
trace race conditions, because all stream resources will use a single, shared
default context resource otherwise., (*71)
TimeoutConnector
The TimeoutConnector class implements the
ConnectorInterface and allows you to add timeout
handling to any existing connector instance., (*72)
It does so by decorating any given ConnectorInterface
instance and starting a timer that will automatically reject and abort any
underlying connection attempt if it takes too long., (*73)
$timeoutConnector = new React\SocketClient\TimeoutConnector($connector, 3.0, $loop);
$timeoutConnector->connect('google.com:80')->then(function (ConnectionInterface $connection) {
// connection succeeded within 3.0 seconds
});
See also any of the examples., (*74)
Pending connection attempts can be cancelled by cancelling its pending promise like so:, (*75)
$promise = $timeoutConnector->connect('google.com:80');
$promise->cancel();
Calling cancel() on a pending promise will cancel the underlying connection
attempt, abort the timer and reject the resulting promise., (*76)
UnixConnector
The UnixConnector class implements the
ConnectorInterface and allows you to connect to
Unix domain socket (UDS) paths like this:, (*77)
$connector = new React\SocketClient\UnixConnector($loop);
$connector->connect('/tmp/demo.sock')->then(function (ConnectionInterface $connection) {
$connection->write("HELLO\n");
});
$loop->run();
Connecting to Unix domain sockets is an atomic operation, i.e. its promise will
settle (either resolve or reject) immediately.
As such, calling cancel() on the resulting promise has no effect., (*78)
Install
The recommended way to install this library is through Composer.
New to Composer?, (*79)
This will install the latest supported version:, (*80)
$ composer require react/socket-client:^0.7
More details about version upgrades can be found in the CHANGELOG., (*81)
This project supports running on legacy PHP 5.3 through current PHP 7+ and HHVM.
It's highly recommended to use PHP 7+ for this project, partly due to its vast
performance improvements and partly because legacy PHP versions require several
workarounds as described below., (*82)
Secure TLS connections received some major upgrades starting with PHP 5.6, with
the defaults now being more secure, while older versions required explicit
context options.
This library does not take responsibility over these context options, so it's
up to consumers of this library to take care of setting appropriate context
options as described above., (*83)
All versions of PHP prior to 5.6.8 suffered from a buffering issue where reading
from a streaming TLS connection could be one data event behind.
This library implements a work-around to try to flush the complete incoming
data buffers on these versions, but we have seen reports of people saying this
could still affect some older versions (5.5.23, 5.6.7, and 5.6.8).
Note that this only affects some higher-level streaming protocols, such as
IRC over TLS, but should not affect HTTP over TLS (HTTPS).
Further investigation of this issue is needed.
For more insights, this issue is also covered by our test suite., (*84)
This project also supports running on HHVM.
Note that really old HHVM < 3.8 does not support secure TLS connections, as it
lacks the required stream_socket_enable_crypto() function.
As such, trying to create a secure TLS connections on affected versions will
return a rejected promise instead.
This issue is also covered by our test suite, which will skip related tests
on affected versions., (*85)
Tests
To run the test suite, you first need to clone this repo and then install all
dependencies through Composer:, (*86)
$ composer install
To run the test suite, go to the project root and run:, (*87)
$ php vendor/bin/phpunit
License
MIT, see LICENSE file., (*88)
Wallogit.com
