Changes between Version 9 and Version 10 of TracDev/ComponentArchitecture

Timestamp:

Jul 4, 2007, 4:31:40 PM (17 years ago)

Author:

Christian Boos

Comment:

Replying to Dave: implementing an Interface and declaring an extension point for an Interface are completely orthogonal; a Component can do one or the other, or both for a given Interface.

TracDev/ComponentArchitecture

@@ -175 +175 @@
 }}}
 
-Note that it has a list of extension points implementing {{{IPermissionRequestor}}} ([browser:trunk/trac/perm.py:r5790#L40 in context]):
+Note that this `Component`:
+ 1. implements the `IPermissionRequestor` interface
+ 1. has an extension point for registering all the Components implementing {{{IPermissionRequestor}}} ([browser:trunk/trac/perm.py:r5790#L40 in context]):
 {{{
 #!python
@@ -188 +190 @@
 
 When we use {{{PermissionSystem}}}, the plugin system will have automatically gathered up all implementations of {{{IPermissionRequestor}}} and placed them in {{{PermissionSystem}}}'s list of {{{requestors}}}.
-
- '''Notes that I hope a Trac dev will check:'''
-   * ''As far as I understand,the line in {{{PermissionSystem}}} that declares it to implement {{{IPermissionRequestor}}} is completely superfluous except for documentation purposes, because it will always be used directly''
-   * ''Does something avoid putting {{{PermissionSystem}}} in its own list?'' [[br]]—dave 
+In this specific case `PermissionSystem` will be part of that list as well, because it implements that interface as well. In no way a Component is bound to implement the interfaces it declares an extension point for, the two operations being entirely independent. But when that make sense, it's entirely possible to do so.
 
 Next in {{{PermissionSystem}}} there is a declaration of an {{{ExtensionOption}}} called {{{store}}}: