[Zope3-dev] ObjectHub: Kill the plugins!

[Steve Alexander]

> PROPOSAL: Eliminate the concept of ObjectHub plugins.  The ObjectHub has
> a simple contract: keep track of integer-to-path mapping, act as a
> transparent event channel, and generate hub events for its subscribers. 
> That's it.  Any clients doing other tasks live elsewhere, using the
> ComponentArchitecture infrastructure, and have their own interfaces.

So, is another way of thinking about this to still have what were 
formerly known as "PlugIns", but to have them in a different place, or 
in different places?

I like the idea of keeping the ObjectHub very simple, and I believe we 
discussed this before, with many points in its favour.

If we agree that this is the way forward, then I think we need to design 
a service for the other role of the obejecthub+pluigins: answering Queries.

So, the default Query service would consist of a container for Plugins, 
many of which are subscribed to the ObjectHub.

As components outside of the ObjectHub were always allowed to subscribe 
to ObjectHubEvents, in the new scheme of things, we have just split the 
original ObjectHub into two parts: focused objecthub, and query service.

--
Steve Alexander