On Nov 25, 2007 6:06 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto:
<snip> > > 4 XMLVirtualUserTable, UsersFileRepository, UsersLDAPRepository were > > provisionally included in library. not sure this is right but i'm not > > sure that there's enough critical mass to create components to contain > > them yet > > Creating modules with very few classes will only increase the complexity. complexity isn't quite the right word. the level of complexity is innate in the code and cannot be altered by re-arrangement. creating small, focussed modules increases the granularity of the components in the system. small components have the advantage that they are each easy to understand since they are better focussed. they also allow more precise control over dependencies. a finely grained components system has some disadvantages. lots of small, focussed components obscures high level relationships within the system. > > 5 unsure about the granularity of avalon-user-function and > > jdbc-user-function. lots of small components allows precision but > > perhaps might be better to aggregate into large units including all > > backend implementation of the same type. for example, > > avalon-backend-function including all the avalon* implementations > > (AvalonRepository and so on). > > > > opinions? > > IMO it's better to aggregate jdbc-user-function to avalon-user-function. why? (other than an dislike of finely garined component systems) - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
