On Sep 4, 2008, at 11:21 AM, Mark H. Wood wrote: > On Thu, Sep 04, 2008 at 11:07:00AM -0700, Mark Diggory wrote: >> Best to point at the http location unless one has commit rights... > > Thanks. I cut'n'pasted from 'svn info'. Will try to remember this. > >> On Sep 4, 2008, at 10:53 AM, Mark H. Wood wrote: > [snip] >>> (Is there an agreed-upon term for the place where a plugin plugs >>> in?) >> >> Not sure of your meaning... >> >> PluginManager is where they are configured ATM. > > Configured, yes. But, when there is code that plugs in, there must be > code for it to plug *into*. Is the latter a "socket", a "plugin > site", a "plugin port"...? > > The code added in this prototype includes some sample plugins, but its > main thrust is to provide places that call into PluginManager to > invoke the configured plugin. Do those places, individually or > collectively, have a name?
Right now I think its very undefined because the PluginManager actually uses some low level reflection to bring the plugins into existence regardless of what they are for. Just speculating... In the future, this may be what we refer to as a ServiceProvider, and it would probably be implemented as a SPI (Service Provider Interface). -Mark ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
