Timeline for Boto connect_xxx method and connection pools
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2014 at 12:58 | comment | added | malthe | @TuukkaMustonen since this patch the connection object uses a pool such that each connection is used only by a single thread at a time. | |
| Nov 10, 2014 at 11:13 | comment | added | Tuukka Mustonen |
@malthe Got any references to point to about that (AWSAuthConnection being thread-safe)?
|
|
| Sep 18, 2014 at 11:34 | comment | added | malthe |
The connect_xxx methods return an instance of a subclass of AWSAuthConnection which is indeed thread-safe. You should only do this once per process (and connection arguments) – not in every thread. The connection pool is not stored on the class level.
|
|
| Aug 25, 2014 at 16:42 | comment | added | Michael Waterfall | Are there any documentation references available for this information? | |
| Jul 24, 2012 at 22:08 | comment | added | Caleb Wright | Thanks for the answer! And thanks for boto itself, I couldn't live without it. Your mention of threads prompted another question on essentially the same topic, here. | |
| Jul 24, 2012 at 4:04 | vote | accept | Caleb Wright | ||
| Jul 24, 2012 at 2:36 | history | answered | garnaat | CC BY-SA 3.0 |