durusmail: quixote-users: Quixote best practices?
Quixote best practices?
2003-11-07
2003-11-07
2003-11-07
2003-11-11
2003-11-11
2003-11-11
2003-11-12
2003-11-11
2003-11-12
2003-11-13
2003-11-07
Quixote best practices -> HTML menu
2003-11-07
2003-11-07
2003-11-07
Quixote best practices?
Martin Maney
2003-11-07
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?

I've used classes in a couple of places, though so far that's been
mostly for trees with large, data-driven name spaces (or they might be
thought of as argument tails to the distinguishing command name -
depends on which eye you look at it with).  For a larger application, I
think I would be inclined to separate the URL traversal from the rest
of the app anyway, and classes would probably be a natural way to
package the functionality for use by the traversal layer, but that's
only a thought experiment so far.  :-)

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

You can do almost anything with q_lookup() - which might be another
motivation for a separate Quixote traversal layer.

--
The Internet discourages reflection and deep thought. It
encourages just glossing over, as quick as possible. The
Internet is a terrific way to look up facts and a terrible
way to get a story.  -- Clifford Stoll


reply