Hi -

> --------- Note from Tom Jenkins:

> Around this time every year our company re-evaluates our tools,
> platforms, etc.  We're a Zope shop (and quite successful).  Because of
> how we develop for Zope, I don't believe we're getting any of the
> special benefits but we still get all the hassles.  (ie we do NO work
> through the web).  Bringing new people on board is a real PITA.

I am developing a fairly complex intranet app (ultimately also to be
exposed on the public WWW), and have recently switched from Zope to
Quixote. After trying many ways of implementing my app using Zope
resources, I had ended up using bare-bones folders containing almost-empty
"documents" which simply called "external methods" to generate all
their content. I was unable to use mxODBC and mxDateTime with Zope and
was confined to an older version of Python than I wanted.

Quixote is very easy to figure out, and it is basically all the stuff
that I wanted from Zope, with no goofy extras. I was going to blow off
PTL, but quickly found it to be quite handy and trouble-free. It has
been very easy to hack my "external methods" to create a Quixote
application, and now I am able to run Python 2.2.2 and also use my mx
tools.

> This past weekend I started seeing the progress of various projects.  I
> missed Quixote last year, so i'm coming in to the evaluation cold...
> which according to mailing list is a good thing because of the .5
> release 

Yes.

> ...Oh what is everyone
> using as the adapters: SCGI, FastCGI, mod_python, other?

For the intranet app, I am using a customized version of the Quixote
medusa_http server with Medusa 0.5.3, which does everything that I
need and - as far as I can tell - is about the same as the Zope
server.

> ...I think I may "sneak" it in via some small internal projects 

Probably a good plan.

Good luck!

Jim Dukarm
DELTA-X RESEARCH