Well I honestly hadn't considered that. So, I suppose changing to to a mix-in inherited by folder is better. However, you should know that the crux of this change is really to the publisher, the mixin is just the management piece. *any* object can define a browser_default hook that overrides 'index_html', not just objectmanagers. -Casey Jeffrey P Shell wrote:
On 4/16/02 8:53 AM, "Casey Duncan" <casey@zope.com> wrote:
The implementation adds the API to manage browser default for all objectmanagers. However, no browser_default handler is actually added to the object unless you specify a default other than "index_html"
What was the specific "undesirable effects" you were seeing?
If it is agreed that this management should apply to folders rather than all object managers, then I can make this change. In that case using a separate mix-in makes sense to me. It could even be registered for use as a base class for ZClasses then, which would be some advantage I suppose.
+1 for the separate mix-in. I use ObjectManager as a base class frequently for non-folderish objects, for which the whole 'death to index_html' notion is moot.