Hi David, In general, if your application is 'vertically separated' - eg, distinct apps handling distinct functionality - this approach is fine. It's 'horizontal separation' - where an app is split into several apps, all handling the same requests - that we're generally concerned about.
-Nick Johnson On Tue, Nov 10, 2009 at 1:35 PM, davidgm <[email protected]>wrote: > > Hi there, > > I'd like to provide several services-features-functions with GAE apps. > One app is in charge of a few basic services, including a custom > authentication. > I would like to provide some other services with different apps, for > isolation and code manageability reasons. > Those services are independent but need authentication tokens from the > first app. They may also transmit few data to the first app, for > reporting purpose. > > All those apps will have completely different code and purpose, with a > small common library. > However they will sometime get and send data to the main app. > > From the terms of service: "4.4. You may not develop multiple > Applications to simulate or act as a single Application or otherwise > access the Service in a manner intended to avoid incurring fees." > > Is this architecture violating the point 4.4 of TOS ? > > Thanks > > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
