CMFEditions makes heavy use of CMFUid, though if an alternate
preferred uid generation mechanism were decided upon, it likely
wouldn't be hard to switch.
On 4/26/06, Jens Vagelpohl <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 26 Apr 2006, at 07:40, Martin Aspeli wrote:
> > On Tue, 25 Apr 2006 20:21:09 +0100, Martin Aspeli
> > <[EMAIL PROTECTED]> wrote:
> >> On Tue, 25 Apr 2006 16:33:01 +0100, David Pratt
> >> <[EMAIL PROTECTED]> wrote:
> >>> Hi Jens. Z3 has it own uid facilities. I guess folks could pick
> >>> this up through five could they not? Its all moving in that
> >>> direction in any case.
> >> Plone doesn't have UID, but Archetypes does. This is used
> >> primarily for the reference engine, and it's one of the things
> >> we'd really like to componentise out to make it independent of
> >> Archetypes. I'd say we should aim to have one UID implementation
> >> at the Zope3 level and all use that, if it's feasible. I'm not
> >> quite sure which part of Z3 you're talking about though, so I
> >> can't comment on whether it's feasible.
> > ... and Raphael says CMFEditions may depend on this.
> Depend on what exactly..? Archetypes UIDs? Z3 UIDs? CMFUid?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> -----END PGP SIGNATURE-----
> Zope-CMF maillist - Zope-CMF@lists.zope.org
> See http://collector.zope.org/CMF for bug reports and feature requests
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests