On Thursday, August 11, 2016 at 3:40:48 PM UTC-4, Nikolaus Rath wrote: > > On Aug 11 2016, pisymbol <[email protected] <javascript:>> wrote: > > I know this is going to sound strange, but is there anything technically > > blocking s3ql from using the boto3 SDK for its backend implementation > > (s3/s3c). > > That is quite possible. As a matter of fact, S3QL was actually using > boto in some distant past. However, the code got a lot nicer when I > moved away from it, so I see no reason to bring it back. >
I understand. However, Amazon wants enterprise class solutions to use boto3. I'm not sure why!? Another issue is that S3 solutions need to push usage statistics via custom user-agent metadata headers. Is there anyway to specify a user agent header to every s3ql request? I'm thinking that this might be a good feature regardless. I suspect if not, it could be added to the s3ql configuration file as an option per location. -aps -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
