Predis Async Versions Save

This is a bug-fix releases addressing a couple of issues in specific corner cases:

• PHP emitted E_WARN notices when an early error occurred while creating the underlying socket, such as trying to use a non-existent or inaccessible UNIX domain socket file or when the TCP/IP stack is running out of resources (e.g. port exhaustion).
• Commands queued during the connect() operation were discarded by the client because the underlying socket was being set as readable as soon as the connection was fully established even if the buffer was not empty.

This is another important bug-fix release addressing the client getting stuck in an exception loop when it is unable to connect to the specified port of a server (connection refused error).

You can find a better description of the issue in #8.

This is an important bug-fix release addressing an erroneous handling of socket streams when the write buffer is empty, leading to 100% CPU usage spikes. This bug was introduced in Predis\Async v0.2.0 and does not affect v0.1.0.

You can find a better description of the issue in #5.

Predis\Async has been updated to depend on react/event-loop v0.3.x.

Actual changes are quite minimal as the only breaking change for us in the switch to the newer react is in the timers used to control connection timeouts.

This is the first versioned release of Predis\Async, depending on react/event-loop v0.2.x.