RFC: centralise registries

[Robert Collins]

On Tue, 2009-04-14 at 09:58 -0600, Brian de Alwis wrote:
> On 14-Apr-2009, at 3:30 AM, Robert Collins wrote:
> > I think actually the root of the issue is that there is no way for a
> > plugin to say 'I would register with some X but I don't want to  
> > trigger
> > that X'. twisted achieves this by plugin metadata - plugins are a Y,  
> > and
> > this is memoised and then the plugin is called into for Y  
> > operations. I
> > think this is overly constraining.
> 
> 
> FWIW: Eclipse uses XML to represent plugin extension metadata to defer  
> the overhead from loading jars until absolutely necessary.  It's a  
> powerful model and seems to correspond very well to the existing  
> bzrlib registries.  So switching to an XML description wouldn't  
> require too much work, once the actual XML metadata parsing has been  
> written.
> 
> Each plugin provides an XML descriptor, found in the root of each  
> plugin and called plugin.xml.  These plugin.xml are read in at first- 
> load.  The plugin.xml defines: extension points, which are essentially  
> well-defined names, and extensions, which provide extensions to those  
> extension points.

This however is what twisted does that I don't like - rather than being
'a plugin is come code, run it', it is 'a plugin provides interfaces X,
Y, Z only' which is much less duck typing & pythonic.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090415/6de15d3c/attachment.pgp