On Jan 3, 2005, at 10:28 AM, Jason Sibre wrote:

> would be.  I will grant you that in a truly large app, subclassing the
> publisher would be the quickest way to get 2.x compatibility.  Sorta.
> You're
> really just stalling with that approach, unless you plan on
> maintaining your
> own custom version of Quixote eventually.

In Quixote 2, the Directory class, not the publisher, is what you would
subclass.  Quixote 2 doesn't really have an object model in the sense
that Quixote 1 does.  The Publisher expects a _q_traverse() on the root
directory, and nothing more.  All of the
export/lookup/access/resolve/traverse
behavior is totally under the control of your application.  The
Directory
class just provides a default pattern.