Hello,

        I'm currently checking the different Python-based tools to write web
applications, and am taking a look at Quixote. After going through a
successful install of demo.cgi + online docs + archives of the mailing
list, could a kind soul answer the following questions?

1. I understand CGI is slow, and FastCGI is not solid. Since SCGI doesn't
seem to be available for Windows (Neil Schemenauer wrote: "The Python scgi
package will not work on Windows. It uses Unix specific APIs like fork(),
sendmsg(), recvmsg() and socketpair()"), I guess the only alternative is
Apache with mod_python. Is this combo reliable, and does it offer good
performance?

2. Dulcinea lets us access a ZODB easily. Since code lives in Python
scripts and data in a SQL servers, could you give me some reasons to use
ZODB instead?

3. Since alternative Python frameworks like SkunkWeb or CherryPy use an
application server, what would I miss by using a server-free framework like
Quixote (provided I understand things right by thinking that modules like
mod_python are started automatically when Apache starts, and will restart
it in case things go wrong, ie. I don't have to worry about my app no
longer being accessible)?

4. As of Aug 2003, is Quixote validated for use under a Windows-based web
server? I ask because I read the following in the mailing list:  "We are
mainly familiar with Unix, and develop and deploy Quixote under Linux.
However, we've had several reports of people using
Quixote under Windows, more-or-less successfully. There are still a few
Unix-isms in the code, but they are being rooted out in favour of
portability."

5. If some of you have good experience with Python-based alternatives
(SkunkWeb, CherryPy, Webware + Cheetah, Twisted, Draco, Albatross,
Karigell, PyWeb, JonPy), can you tell me why I should favor Quixote over those?

Thank you very much for any tip
Fred.