On Mon, Jan 28, 2002 at 02:53:59PM -0800, David Ascher wrote:
> -- My request for Quixote's evolution is a little more built-in tools
> that make some things easier, like examples for how to persist the
> SessionManager, dealing w/ users & logins etc.  Something like a
> "standard library" of tricks which encapsulate knowledge that seasones
> web developers know that the rest of us don't.

Moving some of our ZODB related code into Quixote would probably help
the most.  We have a Publisher subclass that overrides some methods in
order to do some ZODB things.  We also SessionManager and Session
subclasses that are meant to be persistent in a ZODB.

> -- More generally, the biggest problem I have with Quixote is that that
> I have with all web dev't -- the compile/run/edit cycle is lengthened
> too much by the need to work with the browser (forget cookies, etc.).

I don't find this a problem after programming with Quixote for a while,
even when using FastCGI instead of CGI.  I have an editor macro that
restarts the Quixote process that I hit after saving a file.  For our
application, automatically forgetting the cookies would make things
painful (you would have to login again, for example).

Why can't your application forget cookies when it restarts?  The browser
would then be given a new one that overrides the one it currently has.

  Neil