2 ms·
The transport for this service is HTTP? I imagine most competitors use that as well, right? How does encoding factor in here? I have to transcode my data to
by wyldfire 12y ago
The transport for this service is HTTP? I imagine most competitors use that as well, right? How does encoding factor in here? I have to transcode my data to base64 in order to put it in or take it out, I assume? I "know" I'd only get billed for the data stored as the original octet/binary encoding. But what about the egress fees? Encoded or decoded data is the input for the billing?
- beolab1700 12y agoThere is no need to base64 encode the data on the way in or way out. I cannot think of any APIs that use base64 encoded requests or responses.
- Guvante 12y agoHTTP can transfer arbitrary binary data just fine. There is no need to encode it. I don't know which they use but HTTP traditionally uses a `Content Length` or an empty chunk to represent the end of data.