Namespace amalgamation

[cboden]

Merge the SocketClient and HttpClient into the Socket and Http namespaces respectively.

/Socket
        ConnectionInterface
        Connection
        ConnectionException
        /Server
                ServerInterface
                Server
        /Client
                ConnectorInterface
                Connector
                SecureConnector
                StreamEncryption

/Http
        /Client
        /Server

[cboden]

I also wouldn't mind renaming the Socket namespace. It doesn't quite make sense. It's a remote connection, not a socket. It's extending Stream, where streams are a higher level abstraction that (can) use sockets underneath as the transport.

[igorw]

What would socket be renamed to? Its general meaning is generally "network connection" which I think is accurate.

[igorw]

Still really dislike the React\Socket\Server\Server btw.

[cboden]

I'm not sure if this is feasible yet, but what about removing the Socket namespace all together. Server would live somewhere in the Stream namespace? TCP/Socket implementation details can be hidden in the API.

[clue]

There's ongoing effort to merge the SocketClient component into the Socket component, see reactphp/socket#74 for more details 👍