Andrew, Ok, thanks for the heads up. In my case, I end up needing two blob store contexts, since I have different blob stores in different regions (the context appears to be region specific, at least in my use with Rackspace). So I should essentially create these as singletons, and send data as appropriate.
Thanks, John On Sun, Jan 26, 2014 at 9:44 PM, Andrew Gaul <[email protected]> wrote: > Instantiating a BlobStoreContext performs several requests such > authentication and populating metadata like bucket locations. This > process has some overhead so users should issue many requests against a > single BlobStore. After instantiation each BlobStore request, e.g., > getBlob, issues an HTTP request, creating an HTTP connection as > necessary. From a functional perspective users should not worry about > the underlying HTTP connection pool reconnecting. If an authentication > token expires jclouds will automatically renew it using the provided > credentials. > > On Sun, Jan 26, 2014 at 09:30:08PM -0500, John D. Ament wrote: >> Hi all, >> >> Per the docs here: >> http://jclouds.apache.org/documentation/userguide/blobstore-guide/ >> BlobStores should be reused for multiple requests, not a single one >> per request. However, most of these requests have a timeout involved, >> where the connection is only good for so long. So, does jclouds >> automatically reconnect to the provider if the session times out? >> >> John > > -- > Andrew Gaul > http://gaul.org/
