Look into a version of Crunchy running on Google's AppEngine

[GoogleCodeExporter]

Google app engine has just been announced: http://code.google.com/appengine/

This might be a way of running Crunchy on a properly sandboxed web
server... We should have a play with this and see what we can come up with.

Even if we don't run crunchy on it, we could maybe use it for a repository
of useful code samples (á la 99 problems).

Thoughts?

Original issue reported on code.google.com by johannes...@gmail.com on 8 Apr 2008 at 1:45

[GoogleCodeExporter]

This needs to be explored, but it is my understanding that Crunchy would not be
supported - as it needs long running processes (e.g. embedded interpreter).

From

http://code.google.com/appengine/docs/whatisgoogleappengine.html
==
# An application cannot write to the file system. An app can read files, but 
only
files uploaded with the application code. The app must use the App Engine 
datastore
for all data that persists between requests.
# Application code only runs in response to a web request, and must return 
response
data within a few seconds. A request handler cannot spawn a sub-process or 
execute
code after the response has been sent.
==
Still it is worth exploring.

Original comment by andre.ro...@gmail.com on 8 Apr 2008 at 1:53

[GoogleCodeExporter]

True, but in practice most crunchy scripts run almost instantaneously (and 
terminal
commands tend to be even faster). We would have to use some clever 
serialisation to
keep track of state though...

Maybe as a backend to an implementation with the code running in silverlight...?

Original comment by johannes...@gmail.com on 8 Apr 2008 at 1:57

[GoogleCodeExporter]

Am going through one of my periodic cleanups of old issues that I started: This 
isn't
really accepted, moving to New.

Original comment by johannes...@gmail.com on 15 May 2008 at 1:14

• Changed state: New

[GoogleCodeExporter]

I've attempted to do this and ran into a time limit for scripts.  While the vlam
processing is "reasonably fast", it is still too slow to be useful in practice.

Original comment by andre.ro...@gmail.com on 26 Jul 2009 at 12:04

• Changed state: Accepted

[GoogleCodeExporter]

This should be resurrected and take inspiration from pywhip. 
http://pywhip.appspot.com/

A tabbed interface could be used so that each page contains one doctest-based 
example
and one imbedded interpreter (with some docs).  The idea is: experiment at the
interpreter (and learn), then go to the testing page.

Before work begins on this, we need to confirm that we can backup the stuff 
saved on
the GAE server - which was not the case when I initially looked at it.

The interface I have in mind is inspired by GvR online:
http://gvr.carduner.net/ui/index.html

Original comment by andre.ro...@gmail.com on 19 Aug 2009 at 12:21