1 / 16

ATLAS and Component Standards

Learn about component standards like CORBA, DCOM/ActiveX, JavaBeans, COM+, and more for a generalized framework. Find insights on pros and cons, usage scenarios, and future outlook.

dvick
Download Presentation

ATLAS and Component Standards

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ATLAS and Component Standards Lassi A. Tuura, CERN

  2. Terminology & Background • Component Architecture  Framework • One framework for reconstruction and analysiscode must be easily moved between the two • Data-centric problem view: • Data objects physicist tend to think about • Calculation objects transform and operate on dataand are external to the data • Transient intermediate data objects Lassi A. Tuura, CERN

  3. Standards We Will Use • Object Database Standard (ODMG) Lassi A. Tuura, CERN

  4. Other Standards • CORBA • DCOM/ActiveX • Java Beans • COM+ Lassi A. Tuura, CERN

  5. CORBA: pros • Relatively stable standard, free brokers exist • Interoperable across languages and platforms • Reasonably sound from OO point of view • Good for client-server apps Lassi A. Tuura, CERN

  6. CORBA: cons • A component architecture, not a framework • Incomprehensible to a casual developer • Speed versus encapsulation issues with small components • With an OODBMS, what does it really by us? • Inadequacy of free implementations versus cost of commercial ones? Lassi A. Tuura, CERN

  7. DCOM/ActiveX: pros • Widely used • Sort of interoperable across languages • Good for client-server apps Lassi A. Tuura, CERN

  8. DCOM/ActiveX: cons • Standard still in fluxespecially ActiveX • Proprietary, limited platform availability • Hideously complicated, well-formed code resembles line noise • Lacking OO support • Like CORBA: only a component architecture, performance limitations, not necessarily well suited to the problem domain Lassi A. Tuura, CERN

  9. JavaBeans: pros • Nice, clean and simple design • Gateways to CORBA and COM exist • Platform independent GUI development comes for free • A promising candidate for the future Lassi A. Tuura, CERN

  10. JavaBeans: cons • Close to being a framework, but still not thereprobably quickly done • Platform independentbut simple only in a pure Java environment • Immaturity and instability of the Java development tools • Unstable and proprietary specification Lassi A. Tuura, CERN

  11. COM+ • Don’t know much yetnot yet available, estimated in large scale use by end of 1999 • Addresses COM’s complexity and OO deficiency problems • Component model approximately as simple as JavaBeans • Simplifications made by changing the C++ language! Lassi A. Tuura, CERN

  12. Alternative Non-Standards • IRIS Explorer • AVS/Express • ROOT Lassi A. Tuura, CERN

  13. IRIS Explorer • Commercial, proprietary component interface • High risk • Not object oriented • Abysmal bang for the buck • Technical deficiencies • Unsuitability to non-visual batch execution? • Virtually all parts of interest to us seem to be available for free or very low cost • Leaves important infrastructure gaps Lassi A. Tuura, CERN

  14. AVS/Express • Nice object and component models • Nice to use • Too expensive • Object model conflicts with OODBMS? • Few components useful to uswould have to develop many more ourselves (seems to be less effort than with IRIS Explorer, however) • Like IRIS Explorer: proprietary, high risk, leaves gaps in the framework Lassi A. Tuura, CERN

  15. ROOT • BAD design Lassi A. Tuura, CERN

  16. Conclusions • General framework with maximal simplicity • Use CORBA, JavaBeans, DCE in areas less exposed to physicist developers: • Online (details: Bob Jones) • User interfaces • Graphics Lassi A. Tuura, CERN

More Related