We specialize in hard to find items
All Categories
The CORBA Reference Guide: Understanding the Common Object Request Broker Architecture
Share Tweet
*Price and Stocks may change without prior notice
*Packaging of actual item may differ from photo shown
- Electrical items MAY be 110 volts.
- 7 Day Return Policy
- All products are genuine and original
About The CORBA Reference Guide: Understanding The Common
Product Description The Common Object Request Broker Architecture (CORBA) is a pivotal technology that facilitates and promotes the development of distributed applications. CORBA has taken a stronghold in the computer industry, primarily because it is a standard architecture that provides common interfaces and descriptions for objects. The emergence of CORBA has been a blessing to the programming community-now there is a framework in which distributed object-oriented applications for many different systems can be more easily constructed. This book offers you the clear explanation of CORBA that you need and provides a complete reference to the standard. The CORBA Reference Guide provides a general background in distributed systems, a technology that is vital for building scalable distributed object systems. The book explains the base architecture as well as the services and facilities that extend this architecture. This explanation also provides historical context discussing why certain features were selected. Of particular note, this book details the most sophisticated security framework developed for any architecture to date. The book also covers interoperability with other ORBs, especially between OLE and CORBA. Additionally, key details about the Object Data Management Group (ODMG) Standard are included. Distributed systems managers will gain a better understanding of CORBA by quickly reading the first section of each chapter and browsing the informative margin notes. Software architects and project leaders will appreciate the in-depth explanations of the various interfaces and the rationale behind CORBA. From the Inside Flap The noblest function of an object is to be contemplated. -- Miguel de Unamuno, from Mist (1914) The motivation to write this book came from a desire to help people understand CORBA and its basis. A great deal of misunderstanding arose in the first few years after CORBA appeared. In the time it took to write this book, however, many people became aware of and well informed about CORBA. The misstatements heard today are not nearly as prevalent as they once were. Still, I believe the need for a book such as this has not gone away. Today people have a number of requests for features they want to see become part of CORBA. Occasionally these features have been given a great deal of consideration before being discarded or shelved. This book tries to record some of the thoughts behind the discarding of several ideas. It does not attempt to examine all of them because that would be an immense task. Rather, the most fundamental appear here. This book is for system architects, designers, and programmers, specifically those working in information systems. It is not a programming guide. Instead, it provides a general background and reference to the architecture and various services. I suspect programmers will find this background material useful but not very meaty. The intent is to present CORBA with enough detail and background to help people fully understand and properly utilize its features. This book started out as an explication for system managers and architects, but then several such books came onto the market. A more in-depth reference instead of a cursory explanation became more interesting. As more and more people began committing substantial resources to constructing systems using this technology, it became obvious that someone was appropriately informing management. The Object Management Group (OMG) submission adoptions include details for both application builders and those implementing Object Request Brokers (ORBs). Frequently the bias is more toward ORB implementers. I attempt to remove most of this unless it is important for a good understanding. In some cases, I may have included too little or too much of this auxiliary information. A separate book that gives good application examples is desirable. Documenting all aspects of the architecture and providing coding examples for each woul
