jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timur Alperovich <notificati...@github.com>
Subject Re: [jclouds] JCLOUDS-1008: Add @Encoded annotation. (#861)
Date Thu, 01 Oct 2015 21:37:36 GMT
@nacx I think you're right -- that does make more sense. The contract then is that the user
can either use the old style path encoding where jclouds will encode the entire path string
once (and not encode "/" in parameters) or encode each parameter individually.

Honestly, I considered changing jclouds to the second model altogether from its current behavior,
but was concerned about breaking any consumers that may rely on the behavior. For example,
in S3 the blob name should include "/" in the request and not encode it (although that could
be resolved with ```@SkipEncoding``` on the parameter level).

Reply to this email directly or view it on GitHub:
View raw message