Re:Introducing Google Cloud Storage Nearline
by wyldfire on Wednesday March 11, 2015 @04:32PM
(#9186985)
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?
[ Parent
| on HN ]
Re:Introducing Google Cloud Storage Nearline
by Guvante on Wednesday March 11, 2015 @05:00PM
(#9187241)
HTTP 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.
Re:Introducing Google Cloud Storage Nearline
by beolab1700 on Wednesday March 11, 2015 @04:45PM
(#9187098)
There 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.