A evolução de componentes

e comparação de arquiteturas

• Esta seção ficou para a próxima edição deste curso
• A intenção é discutir:
  • Object Models, genericamente
    • an interface definition language for describing interfaces
    • a mechanism for inquiring about interfaces and their attributes, i.e., an "interface repository"
    • a code file format for storing code that can be loaded at run-time, i.e., a format for dynamic link libraries
    • a mechanism for locating suitable code files for a given interface, i.e., an "implementation repository"
    • a mechanism for loading code files into memory, i.e., a linking loader
    • a mechanism for version checking of loaded code
    • a mechanism for creating instances of a loaded class, i.e., for the allocation of objects
    • calling conventions for methods of an object
    • a mechanism for navigating between polymorphic types of an object
    • a mechanism for reclaiming unused memory, i.e., for the deallocation of objects
    • message formats, if distributed objects are supported
  • Como vários modelos de objetos fazem essas coisas
    • Comparar JavaBeans e ActiveX
    • Comparar EJB e MTS/COM+ (e CORBA?)

comp-5 programa anterior