There are different notions of component flying around. However, Kruchten's Rational Unified Process (RUP) book defines component as: "A component is a nontrivial, nearly independent, and replaceable part of a system that fulfills a clear function in the context of a well-defined architecture. A component conforms to and provides the physical realization of a set of interfaces."
An object alone doesn't provide a physical realization of a set of interfaces. Components are usually composed of several objects which provide this feature. The replaceable, "pluggability" requirement of a component implies that it be designed with minimal dependencies so that it can be used in many different environments. There is no such requirement on individual objects although this sort of decoupling is a good practice in subsystem design. Component Object Model is a term coined by Microsoft for their COM architecture. You can find ample information on COM at their website. >From: Rahul Desai <[EMAIL PROTECTED]> >Reply-To: Rahul Desai <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Difference B/w Component and Object >Date: Thu, 18 Oct 2001 21:36:13 +0530 > >Hi Gurus, > >Can somebody tell me some precise differences b/w a Component and an >Object? >And also the definition of a Component Object model. > > >Thanks and regrads >Rahul > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
