durusmail: quixote-users: quixote.server.medusa (Re: Pipelining the async HTTP server)
async HTTP server included?
2004-01-06
2004-01-06
Re: async HTTP server included?
2004-01-06
2004-01-06
async HTTP server included?
2004-01-06
Re: async HTTP server included?
2004-01-06
async HTTP server included?
2004-01-07
Re: async HTTP server included?
2004-01-07
2004-01-07
2004-01-07
2004-01-07
Re: Licensing
2004-01-07
2004-01-07
2004-01-07
Pipelining the async HTTP server
2004-01-07
Re: Pipelining the async HTTP server
2004-01-07
2004-01-07
2004-01-08
Re: Pipelining the async HTTP server
2004-01-08
2004-01-08
2004-01-08
2004-01-08
quixote.server.medusa (Re: Pipelining the async HTTP server)
2004-01-08
quixote.server.medusa
2004-01-08
2004-01-12
Re: quixote.server.medusa (Re: Pipelining the async HTTP server)
2004-01-13
Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Re: Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Resolved! Was Re: [Quixote-users] Re: Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Re: Resolved! Was Re: Re: Problem with using quixote.server.medusa vs. standalone medusa
2004-01-14
Pipelining the async HTTP server
2004-01-08
2004-01-08
Re: Pipelining the async HTTP server
2004-01-08
2004-01-08
2004-01-06
Re: async HTTP server included?
2004-01-06
quixote.server.medusa (Re: Pipelining the async HTTP server)
O. Moskalenko
2004-01-12
* Graham Fawcett  [2004-01-08 13:30:22 -0500]:

> I've created a patchfile (-p0) that should add the quixote.server.medusa
> subpackage. Apparently it's too big for the maillist, so I put it at:
>
>   http://fawcett.medialab.uwindsor.ca/quixote/medusa.patch
>
> For fellow Windows testers, an archive of these files is
> (temporarily) located at
>
>   http://fawcett.medialab.uwindsor.ca/quixote/medusa_patch.tar.gz
>
> There are a few extra files that I hadn't realized were needed (Sam
> didn't put all his imports at the top of his source files...).
> xmlrpc_handler is in there, and a few other utility files needed for
> logging (which eventually could be stripped out).
>
> I also added a submodule, server.py, which is a copy of medusa_http.py
> with the addition of a convenience class, Server. Starting a Quixote app
> using this approach is as easy as:
>
>      from quixote.server.medusa import Server
>      s = Server('quixote.demo', port=8080)
>      s.run()
>
> The signature of the Server constructor is:
>
> __init__(self, approot, config_file=None, port=80, enable_ptl=True)
>
> where enable_ptl is a truth value; it will automatically import and
> enable PTL if set to a true value.
>
> Comments welcome!
>
> -- Graham

For some reason I can't get my first ever quixote app ver. 0.01 work
with the medusa server from your patch. Requests just time out. I have
no problem with the standalone medusa, following the instructions posted
by Dave Kuhlman here on Jan 7. I'd like to use the stripped-down medusa
from quixote, so how could I debug this problem?

By the way there is a tiny cosmetic problem in your http_server.py that
is remedied by the patch below. The newlines don't work with forward
slashes on my linux system.

--- http_server.py      2004-01-12 17:42:36.000000000 -0500
+++ /usr/src/Quixote-0.7a3/server/medusa/http_server.py 2004-01-12
17:54:19.000000000 -0500
@@ -584,9 +584,9 @@

         self.log_info (
                 'Medusa (V%s) started at %s'
-                '\n\tHostname: %s'
-                '\n\tPort:%d'
-                '\n' % (
+                '/n/tHostname: %s'
+                '/n/tPort:%d'
+                '/n' % (
                         VERSION_STRING,
                         time.ctime(time.time()),
                         self.server_name,


reply