Reuse OkHttpRequestHandler across multiple GeoApiContext's

[moadi]

Hello,

We're currently using this library across several of our services, and ran into resource exhaustion similar to what folks have reported in this issue.

Our services are in a monorepo and we provide a common class to initialize a GeoApiContext. In some legacy services, we can use different API keys for constructing this object within the same service. Now, instead of creating a new OkHttpRequestHandler for each unique API key, is it safe to create a single OkHttpRequestHandler for the instance/process and pass that to multiple GeoApiContext classes? We'll make sure to shutdown the handler when the process is terminating.

Thanks!

[moadi]

looked at the code, don't think I can do this.