App engine to me is a hosting environmnt first, and an API second. The API alone is no big deal. In fact, it has some annoying limitations that many other api's don't. (I'm not complaining here) App engine's killer feature is the fact that it is hosted within google's infrastructure, with the ability to scale up by adding lots of instances of your app automagically.
The challenge of implementing other languages, as I understand it, is figuring out how to sandbox them, and bring up / take down instances at will. On Oct 12, 1:51 am, jsnx <[EMAIL PROTECTED]> wrote: > I'm curious about the App Engine team's decision to be make > App Engine an API and not a protocol. There must be protocols > underyling all this stuff -- though they may be pretty rough > -- and protocol level access would have facilitated use of > Ruby, PHP, Haskell, Bourne Shell and Perl as well as Python. > > It is true that protocol level access would have perhaps > undermined that app hosting feature of Google App Engine, or > would have complicated it beyond reason. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
