Hi bFlood, 2010/1/19 bFlood <bflood...@gmail.com>: > that is how we will be deploying our app. Users add a specific email > address as a developer and then we load/maintain the source code > remotely. A simple cron request makes a call back to our controlling > app (on GAE) so we can change limits, upgrade features or turn off the > remote app (in the event they subsequently remove the developer email > account and stop paying). There are probably many other ways to combat > this issue
Wow, cool. I've been thinking of setting up one app for a while and letting other Google Apps just add it via their accounts. Separating data for each mapped domain seems to be easy enough, but letting lots of people from different Google Apps Domains log in seems to be the hardest thing to do (so your suggestion above seems to get around this, thanks). For more information about my login issues/problems, see: http://groups.google.com/group/google-appengine/browse_thread/thread/a71984d787536d82/d64828849b924b83 Further to this, I tried OpenID and the federated login, but it seems the IDP stuff (or whatever it is extra in the federated login (discovery?)) isn't liked by the Python OpenID library (yet?). It makes me sad this is so hard to set up. It seems the Google Labs ShortLinks service somehow works exactly how I would like mine to but I'm yet to find an answer as to how they did it. If anyone knows, I'd be very grateful :) > this setup works well in practice. The user pays Google directly for > usage and then licenses the software from us. It turned out to be a > lot easier then running it as a service (single GAE app) and having to > be the middle-man between the user and Google. Trying to estimate how > they would be billed per month was difficult and seemed like a > duplication of the existing infrastructure. Also, a flat fee might > have been more profitable (or not) but IMO does not play to one of > GAE's biggest strengths, true utility billing. Maybe this is the way forward for me. I guess there is also some way to remotely disable the app (e.g. when their license is up) since otherwise the user could just disable your access to the AppEngine control panel. I guess your application has something like this in it? Of course, this solution doesn't scale for hundreds or even thousands of users so I'm kinda hesitant to do it. I'd love if you could reassure me it can be done. :) Cheers, Andy -- contact: Andrew Chilton website: http://www.chilts.org/
-- 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-appeng...@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.
