Hi Ian, Sorry for the late reply. Thanks for the links that you gave. I've gone through them and I'm currently studying the Google Storage API in order to figure out it's implementation. I've also gone through the source code of libs3 in the ceph repo. Due to the excellent clarity of the code, I was able to easily understand the basic flow of how things are working with respect to the S3. Following are the methods that will be implemented under the Google API. GET Service : Lists all of the buckets in a specified project. DELETE Bucket GET Bucket HEAD Bucket PUT Bucket DELETE Object GET Object HEAD Object POST Object PUT Object
The format of the HTTP headers that need to be sent regarding each method have been clearly given in the Google documentation which is quite similar to the S3 API. Regarding the Authorization part, every request that needs to be authorized must have a request header that contains an authentication string. This authentication string can be extracted with the help of Oauth. As written in the project description, that authentication will take up the majority of the project's time, hence I'd like to know the challenges regarding this beforehand since the Google docs focus more on the Oauth authentication from the user's perspective. FInally, since only a few days are left for proposal submission deadline, so I'll fast track my proposal preparation based on your feedback and guidance. Regards Vipul Nayyar -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
