Ivo van der Wijk wrote:
> Secondly, can someone give me an example of a Replaceable object?
Any object that doesn't represent a service-kind-of-thing.
The term "replaceable" is used in the context of acquisition. Making
things non-replaceable is a way of providing a particular service (say,
a MailHost), and ensuring that this service will not be inadvertantly
shadowed by something else (a DMTL Method perhaps) in a higher-up folder.
The concept of "replaceable" isn't needed in Zope 3, as services are
kept separate from content.
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -