id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
82	build an app server?	Brian Warner		"I've been thinking it might be handy to build a sort of ""application server"", using Foolscap as the transport. Something like my limited understanding of the Waterken server.

Foolscap demonspawner: run multiple services from a single tub, kind  
of like the waterken server. Once the tub is running, use 'tool add'  
to allocate a swissnum, create a directory (with a hash of the swiss),  
populate it with a skeleton .rpy, then print the furl. The rpy should  
define a Service+Referenceable that will be started the first time  
someone hits the furl. Think Waterken for foolscap. Also, once remote  
promises are in, a CLI tool that evals ""p.foo(12).bar(34)"" and prints  
the result would be handy.

This could be a superset of the current file-transfer and command-runner demos
in the docs/ directory. Maybe something like:
{{{
flappserver create DIR
flappserver start DIR
flappserver add shell 'ls /home/public'   -> FURL
flappserver add file-upload /home/inbox   -> FURL
}}}

where the 'shell' and 'file-upload' words are keys that map to some piece of code. The 'flappserver add' command would create a file in its swissnums/ directory, filled with
python code that instantiates an object to do the desired operation.
"	enhancement	closed	major	0.4.2	usability	0.2.9	fixed