jamiegau
commented
2 years ago After more study of the library, I am of the understanding that I could create a singleton class for each device I require a connection with keeping a
client = Client('http://localhost:8181/soap/helloservice?wsdl', username='bob', password='catbob')
variable active and as such keeping the initial login active and the http/https connection alive. Allowing me to reuse the connection and not having to re-login every time I need to call a method.
If that's the case, we can close this query. Thanks.
I have a need to use keep alive and connection pooling. So when I open new calls to a soap service, the requests library in use attempts to reuse already existing connections.
I have looked over the code. It's a little beyond me. So I am asking here is this feature is actually present. The manual does not mention it, apart from caching the wsdl's.. From my inspection, it looks like a non connection-pool library is used and that does not implement connection pooling.
After looking though the code more, it looks like implementing a connection-pool solution would be quite involved, likely beyond me. Could I have a comment form a key developer on this topic and the likely best path to implement this feature?
My initial reaction is to move it to urllib3 as it does support connection pooling.