On Fri, Nov 07, 2003 at 08:40:09AM -0600, Skip Montanaro wrote:
>     * 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?

We tend to keep things pretty flat.  We use packages for static
things and _q_lookup and objects for dynamic things.

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

We mostly use mod_rewrite.  Getting Quixote to do the redirection
should be easy as well.  If you have a lot of redirects it's
probably more efficient to build something in Quixote.  I've posted
some example code to the list for doing redirects.

>     * 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.

Quixote does not do this.  It does provide an easy way to set the
'Expires:' header of the response but that's not really the same
thing.  Building something like Mason has for Quixote should not be
difficult, we just haven't felt the need for it yet.

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

Quixote has support for session management and it's pretty well
documented.  See the session_mgmt file.

> My apologies if I'm asking questions which have been repeated ad
> nauseum.

Don't be shy asking questions.  There are people reading the list
with a lot of Quixote experience.  It would be good for the
community if some of their knowledge was published in a public form.

  Neil