On Thu, Jun 26, 2014 at 2:37 PM, Shawn McElroy <sh...@skift.io> wrote: > > Basically, i would have a web app on appengine, where you can create an > app backend. Creating a new backend will create a new DB table or something > similar (potentially nosql), so each app will have its own database to > connect to. And in this app configuration, i could control various settings > and behaviors about how it returns data. > > What I do not see, is that I personally see these as seperate 'apps'. > > But when a new user app is created, it should create their own DB and > their own 'bucket', essentially for their app to live in. >
It sounds like you're describing namespacing: partitioning off data inside an application: https://developers.google.com/appengine/docs/python/multitenancy/ . This will be one single application (loaded onto a single app ID) but data will be handled separately. For an example, see how the datastore handles this: https://developers.google.com/appengine/docs/python/multitenancy/multitenancy#Python_Using_namespaces_with_the_Datastore ----------------- -Vinny P Technology & Media Consultant Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
