Difference between Objects and Components


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: Difference between Objects and Components

  1. #1
    Join Date
    Feb 2006
    Posts
    17

    Difference between Objects and Components

    I want some clarification.

    When it comes to enterprise applications why objects are being replaced by components.

    Can any body helpme out

    Thanks in advance
    subhakar

  2. #2
    Join Date
    Feb 2006
    Location
    Cologne - Germany
    Posts
    271
    difference lies in the perspective.
    while an object is an real programmatic entity, an instance of an class, a component is a view of some more complex code. a component can consist of more than one object. component is a more abstract term. you could say my webserver is a component of an bigger enterprise architecture. but you also could say a button is a component. usually components encapsulate some reusable functionality, are autonomous but can be connected to other components. i know, objects can do so as well. but object are, next to primitive types, the smallest entities available in programming languages, while components are usually bigger and have more common functions.
    refer to the wikipedia definition. it says:
    A software component is a system element offering a predefined service and able to communicate with other components. Clemens Szyperski and David Messerschmitt give the following five criteria for what a software component shall be to fulfill the definition: Multiple-use, Non-context-specific, Composable with other components, Encapsulated i.e., non-investigable through its interfaces, A unit of independent deployment and versioning
    .
    Very important for me is the "a system element offering a predefined service and able to communicate with other components". so the component encapsulates the functionality as an (aotonomous) service, connected to others.
    There also is the following definition:
    A component is an object written to a specification. It does not matter what the specification is: COM, Java Beans, etc., as long as the object adheres to the specification. It is only by adhering to the specification that the object becomes a component and gains features like reusability and so forth.
    So you can see that components can be implemented as single or multiple objects and it's just the perspective to all of this.

Similar Threads

  1. Beta - Mabry .Net Internet Components
    By Zane Thomas in forum dotnet.announcements
    Replies: 0
    Last Post: 10-17-2001, 11:51 PM
  2. Internet Components - Beta
    By Zane Thomas in forum .NET
    Replies: 0
    Last Post: 10-17-2001, 03:37 AM
  3. ASP vs. VB objects
    By Chad in forum ASP.NET
    Replies: 8
    Last Post: 06-25-2001, 01:37 AM
  4. Data Access Objects 2.0/2.1
    By Chris Brown in forum VB Classic
    Replies: 2
    Last Post: 02-08-2001, 07:47 AM
  5. Components vs Objects
    By Oliver Lennon in forum Enterprise
    Replies: 3
    Last Post: 04-18-2000, 01:30 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center