I'm not so certain that this means that the idea he describes is against the TOS. I put the emphasis on "intended to avoid incurring fees", which is not what he's talking about.
In fact, this exact idea was discussed at the GAE/Cloud Computing Meetup in Palo Alto last month which had several of the core GAE team members in attendance. It was proposed as a valid solution to have one backend REST app server 3 different world facing web apps. It would be good to see some clarification from Google on this point. -Josh 2009/4/13 风笑雪 <[email protected]>: > It's here: > http://code.google.com/appengine/terms.html > > 4. Fees for Use of the 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. > 2009/4/12 DarkCoiote <[email protected]> >> >> Humm.. Didn't remember that, and with a quick (really quick) look >> didn't find that too... >> >> But that make sense, as It would be a way to 'bypass' the quotas and a >> way to do bad things (dos)...and other evil stuff too! lol >> >> But then, with an application like I said - central database, to use >> for score, person info, >> 'virtual currency',etc - what would you suggest to do? >> >> Thanks! >> On Apr 11, 1:15 pm, 风笑雪 <[email protected]> wrote: >> > There is a policy of GAE that you CAN NOT use an app to support another >> > app. >> > >> > 2009/4/11 DarkCoiote <[email protected]> >> > >> > >> > >> > > I thinking about creating a couple of applications that have a common >> > > data-base. >> > > As I'm pretty new at this stuff, I don't have many ideas. >> > >> > > One possible solution would be: >> > >> > > create the applications A,B,C >> > > create an master app. D that controls the central database: >> > >> > > Then, apps A,B,C would query app D to use the database (get, post, >> > > put) >> > >> > > For D I guess an REST solution would be fine (although I don't even >> > > know for sure what >> > > REST is), then A,B,C would use the D REST api. >> > >> > > As the database should not be public, some kind of authentication must >> > > be done to >> > > ensure that D processes only requests from A,B,C (no idea on how to do >> > > this, except from >> > > the stupid method of sending a large known (to A,B,C,D) random string >> > > as a parameter) >> > >> > > Other alternatives to REST would be SOA and RPC, right? from what I've >> > > just read about >> > > these architecture REST would be the best one.... >> > >> > > Useful linkI found around: >> > >http://code.google.com/p/appengine-rest-server/ >> > >> > > Any suggestion will be appreciated ! >> > >> > > Thanks! >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
