[21] APPLICATION ARCHITECTURES UPDATED!
(Part of the CORBA FAQ, Copyright © 1996-99)


[21.1] DOES CORBA DEFINE HIGH LEVEL APPLICATION ARCHITECTURES?

No, it’s infrastructure. Which is good because the history of high-level “one size fits all” architectures hasn’t been very good, has it?

CORBA provides low level request/response communication. It also provides general services that are implemented on top of request/response communication. The actual architecture used within a given application is not defined by CORBA. CORBA leaves these decisions up the application architect.

TopBottomPrevious sectionNext section ]


[21.2] DO COMMON APPLICATION ARCHITECTURES EXIST? UPDATED!

[Recently did some wordsmithing (12/1998) and added comparisons to EJB and removed BOA reference (10/1999). Click here to go to the next FAQ in the “chain” of recent changes]

There are many common application architectures that can be used within a CORBA based application. Some architectures are related to the way in which a CORBA object is referenced, and a few of these are described below.

NON-EXCLUSIVE OBJECTS VS. EXCLUSIVE OBJECTS:

Note: Object level properties such as “non-exclusive” or “exclusive” are orthogonal to the the Object Adapter used to make the CORBA object available to the system.

OTHER ARCHITECTURAL DISTINCTIONS MADE AT THE OBJECT LEVEL:

TopBottomPrevious sectionNext section ]


[21.3] CAN CORBA APPLICATIONS HAVE CALLBACKS? NEW!

[Recently created (10/1999). Click here to go to the next FAQ in the “chain” of recent changes]

Yes. The words client and server are really only applicable in the context of a remote call. In other words, the “client process” can also receive calls on CORBA objects that it implements and hands out the references to.

Also see the section on Notification.

TopBottomPrevious sectionNext section ]


E-Mail E-mail us
CORBA FAQTable of ContentsExhaustiveAlphabeticalSubject indexAbout the authors©TMDownload your own copy ]
Revised Oct 27, 1999