Ultimately the question the TOS is asking is: "are multiple appspot apps being used to circumvent quotas/limits?"
It would seem to me that a facebook-clone app like you describe would see considerable savings by splitting into multiple apps (because of the free quota allotted to each app), which I imaging Google would frown upon. However, if your subapp has different requirements that might justify it being moved to a new app id (for example, a different group of developers who shouldn't have access to the main app's dashboard, etc), you might get some leniency. On Jul 15, 12:00 pm, echeek <xaviereni...@gmail.com> wrote: > In my GAE development, I'm wondering if an offshoot sub-application of > my main application merits being an appspot instance of its own. The > new sub-application is related but doesn't share any data with the > primary app and could be used by other parties. Would moving this sub- > app to its own appspot instance violate the TOS? > > Previous discussion considered unconclusively if a Facebook-clone > where various services (i.e. images, messaging, walls, etc.) are split > to different appspot instances would be allowed. This is similar to my > question however there is no data exchange in my situation. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
