Licensing out which "GAE environment"? The datastore isn't that big a deal - folks have already built a compatible interface with a MySql backend.
The API has lots of other pieces, but their either open-source (memcache), can be used as is (PIL), or not that big a deal (users, except for the google login part). (Yes, google has a pile of servers that provide PIL services, but that's an implementation choice.) The hard part is the infrastructure holding this all together. That infrastruture is Google's "secret sauce" for managing a large amount of computation. You can do without if you're not going to be big, but .... On Feb 4, 7:47 pm, mcamirand <[email protected]> wrote: > If we keep our app in its current form, we can choose from thousands > of hosts. If we migrate to GAE, our app can only work on GAE. We are > bound to Google's pricing, SLA, privacy policy, whims. Why doesn't > Google revolutionize hosting by licensing out the GAE environment? If > the neighbourhood datacentre could offer me a GAE environment, I'd be > converting my app tomorrow. > > Everyone is already amazed by what's been created here. Google > shouldn't wait until someone releases an open-source implementation of > GAE that becomes the new standard for the hosting world, replacing > dedicated servers and virtual private servers. > > -m --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
