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?
A.M. Kuchling
2004-01-07
On Tue, Jan 06, 2004 at 04:44:49PM -0500, Graham Fawcett wrote:
> >It's very kind of you to ask. I forgot to add a comment in the code to say
> >it's published under the same licence as the whole Karrigell framework
> >(GPL). Anyway, feel free to use it and adapt it as you like, and include it
> >inside Quixote. If you find bugs in it I'd be glad to know as well !

Mrr... that's a problem, because it's not clear what "linking" means in the
context of Python.  Can we ask him to relicense the file under a BSDish
license such as the Python license?

--amk


reply