On Thu, 12 Dec 2002 09:53, Peter Donald wrote: > On Thu, 12 Dec 2002 06:02, Dennis Kang wrote: > > Is there any design principle when to use components > > and when to use general classses? > > In a word - no ;) > > A rule I uses is that if an object is; > * never going to be pluggable > * does not have a separate work interface > * does not need the resources of a component (or can be reworked to be like > that). Example resources; logger, servicemanager, configuration etc
... then it should not be an Avalon component. If it has some of the above aspects then it becomes much more difficult to decide. If it has all of the above and coupling to Avalon/Framework is not a problem then I make it a component. -- Cheers, Peter Donald Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. - Fred Brooks, Jr. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
