Why the threading issue is a problem? You can run PHP in CGI mode in single thread, or translate it to native code by hiphop (https://github.com/facebook/hiphop-php/) to prevent the PHP engine initialization overhead, and run the generated code on AppEngine (like you run a Go generated native code). I don't know the deeper AppEngine architecture, but it songs possible.
On jún. 23, 05:30, "Ikai Lan (Google)" <[email protected]> wrote: > The threading issue is a really good point about why a native PHP runtime > won't work on App Engine. If you read the PHP discussion, you'll see why PHP > developers do not want to use Quercus - perhaps you can convince them > otherwise? > > One last note: there is no more distinction between "App Engine" and "App > Engine for Business" due to the pricing changes. Our plan is to release > features that were originally intended for GAE4B only to be paid add-ons. > > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog:http://googleappengine.blogspot.com > Twitter:http://twitter.com/app_engine > Reddit:http://www.reddit.com/r/appengine > > > > > > > > On Tue, Jun 21, 2011 at 9:06 PM, László Fazekas <[email protected]> wrote: > > Partly true, partly not. Usage of ORM in PHP not common as in Java, but > > most of the PHP based system has a an abstraction layer upon the database, > > and if you change it, you can use your existing system on GAE. For example > > you can run Wordpress on AppEngine with Quercus with a relatively small pain > > (seehttp://wordpress-on-quercus.appspot.com/wordpress-2.7.1/). > > > If you develop a new application, you can use ORM which hides the real > > database implementation. For example LWorm ( > >http://code.google.com/p/lworm/) is really small and easy to use > > abstraction tool. If you use it, you can use your application in a standard > > LAMP environment with MySQL, or on AppEngine with Quercus without any pain. > > > Thirdly, it is possible to use memory mapped SQL databases (like HSQLDB) as > > a storage. In this case the db is stored in datastore as a blob. Not so > > efficient, but it can work with small databases. Bu, as I know, Google plans > > to support SQL on AppEngine (maybe only in the AppEngine for Business). > > > So, I think PHP on AppEngine is not an impossible or meaningless thing, and > > not wronger than Python on AppEngine. Quercus is existing thing, you can run > > PHP on AppEngine with it. It is GPL-ed. So, I think, the only think what > > Google should do is officially support it on AppEngine. Maybe it would be > > enough to change the sdk, and create a build script which makes a war which > > includes Quercus and the PHP code. It doesn't songs too difficult, so I > > don't understand why not supported PHP on AppEngine. (PHP support is one of > > the most needed feature on the issues list.) > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To view this discussion on the web visit > >https://groups.google.com/d/msg/google-appengine/-/nvnn6N7lcfMJ. > > > 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. -- 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.
