Better distinguishing between runtime problems

[panvid]

Right now all problems in Http\Client::send() will happen in one Client\Adapter\Exception\RuntimeException with a (often sprintf) string and error code 0.

Examples:

throw new AdapterException\RuntimeException('Unable to Connect to ' . $host . ':' . $port);

throw new AdapterException\RuntimeException('Trying to write but we are not connected');

With this Exception I cannot handle useful reactions in my software.

My Feature Request hopefully triggers the discussion to cluster Exceptions or work with Exception::code to distinguish problems.

[weierophinney]

This package is considered feature-complete, and is now in security-only maintenance mode, following a decision by the Technical Steering Committee.
If you have a security issue, please follow our security reporting guidelines.
If you wish to take on the role of maintainer, please nominate yourself

You can continue using laminas/laminas-http safely.
Its successor will be PSR-7 in a later revision of laminas/laminas-mvc.