Re: putBlob with an already existing object

On Thu, Apr 05, 2018 at 02:12:28AM -, john.calc...@gmail.com wrote: > What is jclouds's general policy with regard to putting a blob to a cloud > service where the blob already exists and the cloud provider doesn't allow > overwrites? > > Seems like it would be nice to be able to treat the

Re: deleteObject with missing object

On Thu, Apr 05, 2018 at 02:04:58AM -, john.calc...@gmail.com wrote: > What does deleteObject do when the object is not present in the cloud? does > it silently return success (as with the corresponding idempotent http verb)? > > When writing a client, one doesn't want to catch an exception

Re: Requiring Java 8 and Guava 21+

On 2018/03/24 19:40:39, Andrew Gaul wrote: > jclouds-dev has a thread on requiring Java 8 and Guava 21+. > when not if. Any comments on this proposed change? I've been using Java 8 for 2 years now and I started late. I can't believe what I was missing out on - Java 8 is

putBlob with an already existing object

What is jclouds's general policy with regard to putting a blob to a cloud service where the blob already exists and the cloud provider doesn't allow overwrites? Seems like it would be nice to be able to treat the operation like it's an idempotent http PUT, but if the service disallows

deleteObject with missing object

What does deleteObject do when the object is not present in the cloud? does it silently return success (as with the corresponding idempotent http verb)? When writing a client, one doesn't want to catch an exception for a missing object and, not knowing what it's for, just retry the operation.