So is it perfectly fine according to the Avalon design principles to have many other methods in the implementation besides the Service and lifecycle methods ?
I wonder why no-one asked that question before...at least I can't recall it :D
sure. Its okay. The cool thing with rigid contracts is that if you're not breaking them, you're doing it right ;)
I try to keep methods at around 8-10 lines. Keeps the code readable.
What is *not good* is /other/ classes (other than subclasses) calling these methods. If its not a lifecycle method or a work interface method, you'll probably want to make the method private, or protected.
Or should the aim be to put the internal functionality of implementation into the lifecycle methods as much as possible ?
no! I try to put as little as possible there ;)
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://articles.leosimons.com/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
