On Aug 13 2016, pisymbol <[email protected]> wrote:
> 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!?
What do you mean with "Amazon wants enterprise class solutions to do
<something>"? Why does it matter to you want Amazon wants, or if Amazon
calls your solution "enterprise class"?
> 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?
Not at the moment, but it would be easy to add if there is a
use-case.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
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.