[Zope3-dev] service names

[Gary Poster]

FWIW, I think this file--in zope/component/--should almost certainly 
only contain the names for the component architecture services.

A similarly named file could exist in zope/app/component that imported 
the component architecture names and defined the application-specific 
ones.  This is the file from which zope code would import their service 
names.

I'm pretty sure that, otherwise, we're letting zope/app stuff creep into 
zope, which is a big no-no.

Agree/disagree?

Gary



sean.bowman@acm.org wrote:
> hello,
> 
> I changed the code and tests to use service names defined in
> zope/component/servicenames.py.  The names I defined are:
> 
>  * HubIds,
>  * Events,
>  * Subscription,
>  * ErrorReports for the ErrorReportingService,
>  * Roles,
>  * Permissions,
>  * Adapters,
>  * Authentication,
>  * Interfaces,
>  * Utilities,
>  * Skins,
>  * Views,
>  * ResourceService for Resources, and
>  * Factories.
> 
> I changed ErrorReports because there's already a
> zope.app.services.errorr.ErrorReportingService, and I changed
> ResourceService because there's already a
> zope.app.publisher.browser.resources.Resources.  It's not a very
> consistent naming scheme -- changing one name to be more like the others
> and another to be less -- so if anybody has better names I'll be happy to
> change things.  Or, perhaps it would better to use qualified names in the
> relatively few cases where there would be a conflict.
> 
> Sean
> 
> 
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev@zope.org
> http://mail.zope.org/mailman/listinfo/zope3-dev
> 
>