I'm just starting out with Quixote.  I plan to convert a couple web sites
from Mason (a mod_perl-based system whose components are a mixture of Perl
and HTML) since the other developers are long gone and they were the Perl
people ;-).  Other than the demo which comes with Quixote, I've not seen
anything else which might provide me with clues to "best practices" for
Quixote sites.  Here are a few random questions which come to mind:

    * Package nesting - Do people tend to nest packages or use other objects
      (classes, for example) to effect nesting?  Or do you normally keep
      your URL space pretty flat so nesting is not an issue?

    * Keeping old URLs - Do you just use mod_rewrite or is there a way
      within Quixote to map (for example),

        http:/www.musi-cal.com/edit.html

      onto Quixote's way of doing things?

    * result caching - Quixote doesn't seem to do any of this.  Mason makes
      caching essentially trivial to handle on a component-by-component
      basis, so you don't need to get your hands dirty setting up caching
      proxy servers and can control caching at a fine-grained level,
      addressing hot spots as they pop up.

    * Session management - Mason uses the perl Apache::Session module.  We
      store our session info in our MySQL database.  Is there any support
      for this?

I'm still working my way through the mailing list archive.  I've gone
through all the SCGI messages and a bunch of the early messages, but still
have 700+ messages to at least glance at, so some of this may be covered
there.  My apologies if I'm asking questions which have been repeated ad
nauseum.

--
Skip Montanaro
Got gigs? http://www.musi-cal.com/
          http://www.mojam.com/
Got spam? http://spambayes.sf.net/