-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 25 Apr 2006, at 15:08, Chris Withers wrote:
Jens Vagelpohl wrote:
I sent an email about this a couple days ago. Basically, I'm down
to one failing unit test in CMFUid and have discovered that
CMFUid is basically broken in 2.0/trunk. I also sent an email on
this issue to the list, hoping that the developers who wrote
CMFUid and lobbied hard to get it included would take notice and
do something about it (or at least acknowledge it), but all I see
is silence so far.
At least I have found what the problem with CMFUid is, and it is
mostly a misunderstanding how it is supposed to work. Mea culpa.
I'm still left with the one failing unit test on the events
branch, though.
Having such an unknown and unmaintained piece of code in the core
of the cmf scares me.
How would people feel about deprecating it for 2.1 and removing it
in 2.3 if no-one steps up who wants it?
Well, I have my own opinion about that, but the course of action
depends mostly on those people who are using it. No one seems to,
judged by the complete silence.
As I have found, it is only used in one specific situations: If you
create a Favorite pointing to a piece of content, then that piece
gets tagged with a UID, and the UID identifies the content piece for
the Favorite. So you can copy/paste/whatever the content and the
Favorite still knows how to find it.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFETjZXRAx5nvEhZLIRAjXvAJwKHXTisxiklmJJSx90XX67IBfD0QCghZzg
8IQx6SgTQpE68yce7gVsEPw=
=Jqjt
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
