-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dieter Maurer wrote:
Tres Seaver wrote at 2006-4-19 15:30 -0400:
...
Is Alec's traversal patch or Dieter's alternative being considered?
I'll note that I have a client who can't move forward from 2.9.1 to 2.9.3 because the changes to traversal semantics in that release break every view lookup in the application (which was originally built on 2.8.x, and works fine on 2.9.1.
I would like to stress that "my alternative" does not change traversal semantics but provides a way for "knowing" component's "__bobo_traverse__" to tell the enclosing framework that "__bobo_traverse__" wants to use the default (and not do anything special). Nothing is changed until a given component uses the feature.
I think the only impact on a site without software which used the feature would be a tiny performance ding (having to wrap the '__bobo_traverse__' call with a 'try:...except:' block). OTOH, since the contract for '__bobo_traverse__' is already insane (it *has* to behave differently for publishing traversal than for "normal" traversal), perhaps this change would reduce that insanity. We need to tweak OFS.Traversable as well, given that it calls '__bobo_traverse__' too. +1 for including the patch in the release tree. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFESD65+gerLs4ltQ4RAok2AJ46fLtHeKrVXhHLToawDHaPd3TpyACgkc36 ONg0Bshqri5i8EyQPbZXmbA= =PB1B -----END PGP SIGNATURE-----