Changes between Version 8 and Version 9 of Specification/AdministrativeComponentSelection


Ignore:
Timestamp:
04/14/2007 11:03:23 PM (7 years ago)
Author:
glyph
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Specification/AdministrativeComponentSelection

    v8 v9  
    6060  * To a reader, this might not be entirely obvious.  One needs to understand {{{getComponent}}} and find the system configuration in order to understand what's going on. 
    6161  * Whoever wrote this had to make a conscious decision to use this system. 
     62  * The failure condition, where {{{ILogger}}} has not been specified, results in an entirely inscrutable traceback.  Why does this code expect an {{{ILogger}}} to be available?  What happens when one isn't?  We've had this problem with Nevow's context object for years now.  Personally, I think that this problem alone should be considered a deal-breaker for this interface.  The "inverted" interface, below, leaves all the problems of location and configuration error reporting to the user, and they all occur ''before'' any application code is invoked, which is vastly superior.  --GlyphLefkowitz 
    6263 
    6364==== Framework-level ("inverted") interface ====