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
Jim Dukarm wrote:

> ---------- Quoth Graham Fawcett: -----------------
>
>>...I propose that we adapt and bundle Pierre's code with Quixote as a
>>built-in Web server for demo and lightweight use....
>
>
>>...I think it would be a great benefit to Quixote window-shoppers if they
>>could have a Works Out of the Box experience; no SCGI, no Apache
>>directives, no Medusa to download. Given the decent scalability of
>>async/polling servers, this would provide not just a demo environment
>>but should be satisfactory for at least small-scale production use.

> ...The benefit is not just to Quixote window-shoppers. A Medusa-like
> out-of-the-box server included with Quixote is just what is needed for
> intranet applications and for various specialized, self-contained
> applications where the user or administrator may not necessarily be
> eager or able to set up and manage a general-purpose HTTP server like
> Apache. An example would be process or lab instrument monitoring.

Agreed! Along the same lines, I've written a few client apps that use an
embedded Web server to provide the UI. Textbook cases of prototypes that
were good enough for production use, and never got rewritten...


> I am in the last desparate weeks of a classic Death March project
> which is being saved from oblivion by Quixote and its Medusa server.

There are the seeds of a great t-shirt slogan in that statement. ;-)


> If Quentel's async http server is made "Quixote-ready," I will be
> happy to bolt it under the hood of my app and test it.

Great. I've e-mailed Pierre to confirm the licensing and/or his
consent, and either Andrew or I will get around to patching his code
post haste.

Regards,

-- Graham



reply