I use zope.component registrations against interfaces a lot.
It's especially useful for things like view registrations if you models have
inheritance hierarchy for their interfaces.
For example it means you can register a default view for a base Interface an
as you develop
more specific views you can register a view at them at a particular subclass
of the base interface.
I think you woul lose that capability with just name based registrations.
Just my 2c worth ;-)
On Fri, Jun 26, 2009 at 4:16 PM, Chris Withers <ch...@simplistix.co.uk>wrote:
> Fernando Correa Neto wrote:
> > I'd like to say that repoze.component ended up being more than just an
> > entry point for people willing to apply AOP on their apps.
> > One can easily exercise the pattern of registering components and
> > looking them up back by just using simple strings rather than defining
> > interfaces just as markers.
> I have to admit, most of the time I just register components against
> classes, rather than interfaces, when using zope.component.
> It'd be interesting to play with repoze.components and see how using
> strings instead feels...
> Repoze-dev mailing list
Repoze-dev mailing list