Document the production-readiness of python-swiftclient as a library
Bug #1696243 reported by
wolever
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
New
|
Undecided
|
Unassigned |
Bug Description
After a few months of using the python-swiftclient library in production, it's very clear that this library is not suited to production environments.
Specifically, the lack of:
- connection pooling
- auth token caching (especially between threads and processes)
- thread safety
Make it quite challenging to use in high-performance, concurrent environments.
It would be nice if these limitations were explicitly documented so other folk can avoid the headaches I've gone through working around these limitations.
To post a comment you must log in.