durusmail: quixote-users: Re: 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
Re: quixote.server.medusa (Re: Pipelining the async HTTP server)
Graham Fawcett
2004-01-13
O. Moskalenko wrote:
> 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?

Hmmm... There are no error messages at the console where you are running the
server?

When you say the requests "time out", do you mean that you are waiting a long
time (longer than 5 seconds) for a response, and your browser indicates that
the connection has timed out? Or does the browser return immediately, but with
no content (or a blank page)?

Would you mind submitting your 0.01 app and the script you used to run it on
top of the quixote.server.medusa package? You could send it to me privately by
e-mail if you wish.

>
> 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,

That's fine with me, but it's not my http_server. ;-) That's the http_server
module from the Medusa 0.5.4 release. (I did comment out an unnecessary import,
but otherwise it's original Medusa code.)

-- Graham




reply