Async Connector to open TCP/IP and SSL/TLS based connections.
Think of this library as an async version of
fsockopen()
or
stream_socket_client()
.
Before you can actually transmit and receive data to/from a remote server, you have to establish a connection to the remote end. Establishing this connection through the internet/network takes some time as it requires several steps in order to complete:
- Resolve remote target hostname via DNS (+cache)
- Complete TCP handshake (2 roundtrips) with remote target IP:port
- Optionally enable SSL/TLS on the new resulting connection
In order to use this project, you'll need the following react boilerplate code to initialize the main loop.
$loop = React\EventLoop\Factory::create();
The React\SocketClient\TcpConnector
provides a single promise-based
create($ip, $port)
method which resolves as soon as the connection
succeeds or fails.
$tcpConnector = new React\SocketClient\TcpConnector($loop);
$tcpConnector->create('127.0.0.1', 80)->then(function (React\Stream\Stream $stream) {
$stream->write('...');
$stream->end();
});
$loop->run();
See also the first example.
Pending connection attempts can be cancelled by cancelling its pending promise like so:
$promise = $tcpConnector->create($host, $port);
$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.
You can optionally pass additional socket context options to the constructor like this:
$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 you want to connect to hostname/port combinations, see also the following chapter.
The DnsConnector
class decorates a given TcpConnector
instance by first
looking up the given domain name and then establishing the underlying TCP/IP
connection to the resolved IP address.
It provides the same promise-based create($host, $port)
method which resolves with
a Stream
instance that can be used just like above.
Make sure to set up your DNS resolver and underlying TCP connector like this:
$dnsResolverFactory = new React\Dns\Resolver\Factory();
$dns = $dnsResolverFactory->createCached('8.8.8.8', $loop);
$dnsConnector = new React\SocketClient\DnsConnector($tcpConnector, $dns);
$dnsConnector->create('www.google.com', 80)->then(function (React\Stream\Stream $stream) {
$stream->write('...');
$stream->end();
});
$loop->run();
See also the first example.
Pending connection attempts can be cancelled by cancelling its pending promise like so:
$promise = $dnsConnector->create($host, $port);
$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.
The legacy Connector
class can be used for backwards-compatiblity reasons.
It works very much like the newer DnsConnector
but instead has to be
set up like this:
$connector = new React\SocketClient\Connector($loop, $dns);
$connector->create('www.google.com', 80)->then($callback);
The SecureConnector
class decorates a given Connector
instance by enabling
SSL/TLS encryption as soon as the raw TCP/IP connection succeeds.
It provides the same promise- based create($host, $port)
method which resolves with
a Stream
instance that can be used just like any non-encrypted stream:
$secureConnector = new React\SocketClient\SecureConnector($dnsConnector, $loop);
$secureConnector->create('www.google.com', 443)->then(function (React\Stream\Stream $stream) {
$stream->write("GET / HTTP/1.0\r\nHost: www.google.com\r\n\r\n");
...
});
$loop->run();
See also the second example.
Pending connection attempts can be cancelled by cancelling its pending promise like so:
$promise = $secureConnector->create($host, $port);
$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.
You can optionally pass additional SSL context options to the constructor like this:
$secureConnector = new React\SocketClient\SecureConnector($dnsConnector, $loop, array(
'verify_peer' => false,
'verify_peer_name' => false
));
Advanced usage: Internally, the
SecureConnector
has to set the required context options on the underlying stream resource. It should therefor be used with aTcpConnector
somewhere in the connector stack so that it can allocate an empty context resource for each stream resource. Failing to do so may result in some hard to trace race conditions, because all stream resources will use a single, shared default context resource otherwise.
The TimeoutConnector
class decorates any given Connector
instance.
It provides the same create()
method, but will automatically reject the
underlying connection attempt if it takes too long.
$timeoutConnector = new React\SocketClient\TimeoutConnector($connector, 3.0, $loop);
$timeoutConnector->create('google.com', 80)->then(function (React\Stream\Stream $stream) {
// connection succeeded within 3.0 seconds
});
See also any of the examples.
Pending connection attempts can be cancelled by cancelling its pending promise like so:
$promise = $timeoutConnector->create($host, $port);
$promise->cancel();
Calling cancel()
on a pending promise will cancel the underlying connection
attempt, abort the timer and reject the resulting promise.
Similarly, the UnixConnector
class can be used to connect to Unix domain socket (UDS)
paths like this:
$connector = new React\SocketClient\UnixConnector($loop);
$connector->create('/tmp/demo.sock')->then(function (React\Stream\Stream $stream) {
$stream->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.
The recommended way to install this library is through Composer. New to Composer?
This will install the latest supported version:
$ composer require react/socket-client:^0.5.2
More details about version upgrades can be found in the CHANGELOG.
To run the test suite, you need PHPUnit. Go to the project root and run:
$ phpunit
The test suite also contains some optional integration tests which operate on a TCP/IP socket server and an optional TLS/SSL terminating proxy in front of it. The underlying TCP/IP socket server will be started automatically, whereas the TLS/SSL terminating proxy has to be started and enabled like this:
$ stunnel -f -p stunnel.pem -d 6001 -r 6000 &
$ TEST_SECURE=6001 TEST_PLAIN=6000 phpunit
See also the Travis configuration for details on how to set up
the TLS/SSL terminating proxy and the required certificate file (stunnel.pem
)
if you're unsure.