> The problem with that is that if any of the sub-aplications > get too complicated or too much traffic, it will affect > all....
The main point of App Engine is that your apps will scale regardless of the traffic (if written correctly). All your sub-applications can reside under one GAE app and scale appropriately. > and the quota will be reached really faster, although there are 'many' > sub-aplications nearly independent of each other.... The TOS prevent developers from aggregating the free quotas across apps to serve a web app. There's a gray area here which only Google can decide. For example, if you did a Google Docs app would that be "independent" of a Google Spreadsheet app? >From the technical standpoint, you could use versioning to have multiple code bases operating at different urls and yet have access to a single datastore. This would also let you mix languages like have a java app under one url and a python app on another. -Bill --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
