base class for un-futuring blobstores

[Adrian Cole <ad...@gmail.com>]

Hi, team.

Many BlobStore commands have chains of gnarly in implementation, and these
are roughly copy-pasted into the AsyncBlobStore.  When removing apis such
as AtmosAsyncClient, you'll probably want to use a class like this to
support the old AsyncBlobStore interface until we can remove it.

https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-swift/src/main/java/org/jclouds/openstack/swift/v1/blobstore/internal/SubmissionAsyncBlobStore.java

If anyone feels it helpful, I can add this to the base blobstore module.

-A

Re: base class for un-futuring blobstores

[Adrian Cole <ad...@gmail.com>]

just takes care of eq/hashCode and clarifies intent.  It is more style than
anything else.

-A


On Mon, Sep 30, 2013 at 2:45 PM, Andrew Phillips <ap...@qrmedia.com>wrote:

> If anyone feels it helpful, I can add this to the base blobstore module.
>>
>
> Benefit of inheriting from ForwardingObject here? Just to document the
> pattern, or can we do other nice Guavish stuff by extending from it..?
>
> ap
>

Re: base class for un-futuring blobstores

[Andrew Phillips <ap...@qrmedia.com>]

> If anyone feels it helpful, I can add this to the base blobstore module.

Benefit of inheriting from ForwardingObject here? Just to document the  
pattern, or can we do other nice Guavish stuff by extending from it..?

ap