How about api `SocketProvider` for `http`? about jodd HOT 1 CLOSED

See 51a3827. There is method open(HttpTransfer) that now accepts custom implementations of HttpTransfer so you can provide one implementation with your custom Socket buildings.

But you are right, you would need to do this every time, it is not possible to set default type of HttpTransfer. The first issue here is that HttpTransfer was designed to be a socket wrapper, so new instance is created for each sending.

Now I start to think that this is not necessary and that HttpTransfer may be stateless Socket provider instead! Then it would contain just methods for creating the socket. And in that case you would be able to set one instance of this socket provider for all Http usage, or eg one instance for HttpBrowser. This also means that send() will go to the HttpRequest. And that there will be default implementation used by HttpRequest.

Or maybe I can split HttpTransfer into two classes: SocketProvider (stateless, global) and HttpTransfer (statefull, created every time on sending, just for sending).

Need to sleep over this one ;)

from jodd.