Python Application Server

[Cameron Laird]

In article <mailman.8176.1233117922.3487.python-list at python.org>,
James Mills  <prologic at shortcircuit.net.au> wrote:
>On Wed, Jan 28, 2009 at 2:42 PM, James Mills
><prologic at shortcircuit.net.au> wrote:
>(...)
>
>> Might I recommend circuits (1) as a general purpose
>> framework that you can build your application on top of.
>>
>> circuits will allow you to communicate with long-running
>> background processes, communicate between processes
>> (by way of a Bridge). All communication in circuits is
>> asyncroneous. circuits has also recently seen the integration
>> of the multiprocessing package from python 2.6/3.0 so you
>> can create processes and have inter-process communication
>> seamlessly. In fact, parts of your system can even run on other
>> nodes (you mentioned clustering).
>
>I should probably mention some of the components available (features);
> * TCPServer, TCPClient
> * UDPServer, UDPClient
> * HTTP, IRC and SMTP protocols
> * Web Server (with limited WSGI support) (depends on parts of CherryPy)
> * Timers, Timer
> * Logger, Debugger
> * ... there are many more components ... :)
>
>Building new components is fairly easy as well.
			.
			.
			.
The big question will be whether circuits qualifies for
the original poster as an "application server".  I agree,
though, that, by the definition as it appeared at the
beginning of this thread, circuits seems to be the best
candidate.