On Thu, Jul 03, 2014 at 07:18:56PM +0200, Nikola Knezevic wrote:
> is there a way to abort a putBlob operation, making sure that the object
> store will not create the blob?
jclouds does not support aborting putBlob, but you appear to have found
a clever workaround below! jclouds 1.7.3 also does
However, the more likely case would be the first one, to abort after
jclouds has made the HTTP call.
I'm not the expert in this area, but in that case I would assume the
result may well depend on how the target provider handles the case
that the client does not send the full payload.
Hope
Hi all,
is there a way to abort a putBlob operation, making sure that the object
store will not create the blob?
For example, if I'm issue a putBlob operation, where I generate the content
and pass it to the Blob through PipedInputStream/PipedOutputStream pair,
would it be possible to abort the o
On 03 Jul 2014, at 19:27 , Andrew Phillips wrote:
> Hi Nikola
>
>> is there a way to abort a putBlob operation, making sure that the object
>> store will not create the blob?
>
> Just to clarify: are you looking to issue the abort *after* jclouds has made
> the HTTP call (i.e. while it's busy
Hi Nikola
is there a way to abort a putBlob operation, making sure that the object
store will not create the blob?
Just to clarify: are you looking to issue the abort *after* jclouds
has made the HTTP call (i.e. while it's busy transmitting the content
to the target), or after you've invok
