durusmail: quixote-users: Re: async HTTP server included?
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: async HTTP server included?
Graham Fawcett
2004-01-06
A.M. Kuchling wrote:

> On Tue, Jan 06, 2004 at 02:11:38PM -0500, Graham Fawcett wrote:
>
>>I propose that we adapt and bundle Pierre's code with Quixote as a
>>built-in Web server for demo and lightweight use.
>
>
> Good idea.  What's the license on the code?  And do you want to work up a
> patch, or should I do it?

Not sure, no license was declared at the ASPN Cookbook site. As a
courtesy, I'll e-mail Pierre to let him know our intentions and to
clarify the licensing terms.

I'm happy to write the patch, Andrew, though I might not have time until
the weekend; I won't feel bad if you beat me to it. ;-)

Best,

-- Graham



reply