Right, that's why I expected to be the initial response. However, if you want to run your own App Engine, you will definitely would want to host your own S3. Like if you will be running your own App engine using CapeDwarf<http://www.jboss.org/capedwarf>
And yes, I know there's the Blobstore API, but that's really a basic storage, you have to write your own authentication layer on top of it, as well as management of objects etc. Actually we will be using the Blobstore to store objects under the hood of 'basket' Also, object storage clients today, almost all of them connect to S3. Example would be s3cmd which can be configured to connect to different 'S3' like the Amazon S3, the RiakCS etc. Ok so the whole point of this is: "Run your own S3 on GAE" and use existing S3 clients to save your buckets and objects. On Wednesday, May 15, 2013 7:07:55 AM UTC+8, Alexander Trakhimenok wrote: > > What the point of the project? There is S3, Blobstore API, Google Drive? > > Why would someone to want emulate S3 on top of GAE? If you need > cross-platform app may be you should thing about creating an abstraction > layer? > > On Tuesday, 14 May 2013 04:51:52 UTC-4, xybrek wrote: >> >> Hello, I am currently working on a project that aims to provide >> S3-compatible object storage API on top of th Google App Engine Platform. >> The project is a fork of littles3 <https://code.google.com/p/littles3/> from >> Jesse Peterson; which is the most complete open source S3 server I found >> for Java. >> >> Also, the aim of the project is to provide a Java open implementation of >> S3 >> (at least most of it, and at least to a usable state) to be able to host >> your own S3 in GAE cloud, JBoss CapeDwarf or with AppScale. >> >> And instead of starting from scratch I started with littles3 which works >> fine already with Tomcat. >> However, it does use a File API and other libraries that are not >> available in the GAE platorm. >> >> I named the project 'basket' and is hosted in Gitub: http://bit.ly/YSE3oY >> >> *Basket *has 3 modules: >> >> *api* >> >> Contains the models and the DAO interface >> >> *filesystem* >> >> Provides concrete implementation of DAO, in the case of littleS3 it was a >> File based DAO, in case of Basket, I chose to use >> Mungo <http://bit.ly/13eSDpr> a JSON document datastore api; since it's >> not possible to save Files with GAE, and GAE Vfs projects seems not active >> anymore. >> >> *web* >> >> Is the module that binds it all. It is the actual GAE app which will >> provide the Restful api to S3 clients. >> >> So, if anyone is interested in joining let me know :-) >> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
