The singleton of httpclient about forest HOT 3 CLOSED

The okhttpclient should init only one client instance and use newBuilder() to make method-level configuration effective and be able to reuse connection pools.
The same, httpclient should init only one client instance and use requestConfig.
In current situation the memory is burst.
I try to submit pr, but unfortunately I find the code needs to be refactored urgently. Sorry for my unsubmitted.

from forest.

Thanks for your advice.

I'll use a cache to store clients. The different requests from a same method will have only one client.
But I found a problem that now one client binds a certain request, but the client can not find the corresponding request object if the client become a singleton instance.

from forest.

The problem has been fixed in latest version 1.5.23

Forest will store different clients to caches of different routes.
Forest request will load the corresponding client from cache.

from forest.