Michael Bernstein wrote:
>
> An example would be an event calendar, where events can be organized
> chronologicaly ( Years>Months>Days) but also according to an event
> category heirarchy (All events>entertainment>music>concerts). These
> heirarchies only intersect at the leaf node of an individual event.
>
> Most product catalogs can be profitably organized using multiple
> heirarchies as well.
>
> So how would you do this in Zope? you could of course represent the
> alternative heirarchies by branching off the bottom of the primary, or
> as folder properties, but that doesn't seem as elegant or maintainable.
> perhaps the answer is some sort of 'pseudo heirarchy' object that could
> be placed at or near the top of the object tree.
>
> What do you all think?

It would be nice if Zope object hierarchy wouldn't be a hierarchy :-)
Instead of a object tree we would have a object lattice. This is viable
since we always have the info about which path to follow in the lattice,
it is the object URL.

It would be great for multilingual web sites. We would have paths to the
same object like:
http://www.mysite.com/section/object            #default language
http://www.mysite.com/french/section/object     #french view of the site
http://www.mysite.com/german/section/object     #german view
 

A simple way to do this: you write a folderish object that is able to "intercept" ORB requests to its children and can process the URL invocation itself? Perhaps by rewriting and redispatching the request? Wouldn't that be enough?

e.g.:

http://www.mysite.com/redirector/chinese/welcome
http://www.mysite.com/redirector/english/welcome
http://www.mysite.com/redirector/esperanto/welcome

    -Gabe