| M. Henning and S. Vinoski. Advanced CORBA Programming with C++. AddisonWestley, 1999. ISBN: 0-201-37927-9. |
....is important in understanding how PIE clients resolve and interact with server side objects; it is also important to provide flexibility in terms of language and server platform to participants in the PIE system. Additional CORBA information can be found in Henning and Vinoski s excellent book [HV99]. One issue in supporting this functionality is providing a naming convention so all CORBA objects can be accessed by any interested clients CORBA provides built in services such as naming, transaction, persistence, messaging, and event notification services which may be useful to supporting ....
Michi Henning and Steve Vinoski. Advanced CORBA Programming with C++. Addison-Weseley, 1999.
....CORBA (www.corba.org) 5 AMPL Session GAMS Session AMPL Kestrel Client GAMS Kestrel Client AMPL Kestrel Solver Object GAMS Kestrel CORBA Internet Interface Kestrel Server NEOS Server Solver Workstation Solver Workstation Solver Workstation Figure 1: Structure of the Kestrel interface. [19], an established and well supported standard. # In particular, we employ IONA s ORBACUS implementation (www.iona.com products orbacus home.htm) Because the CORBA standard is widely available, Kestrel clients can be provided for any of the numerous platforms supported by optimization modeling ....
M. Henning and S. Vinoski, Advanced CORBA Programming with C++. AddisonWesley Publishing Company (1999).
....there is still the danger of not being able to service a client request which makes it desirable to invent a service for resource management, especially since there is currently no distributed garbage collection mechanism for CORBA. One technique of resource management is the Evictor pattern ([1], 2] This approach uses monitor ing to ensure efficient use of resources. It is based on the assumption that resources least recently used (LRU) or least frequently used (LFU) are candidates for automatic release. The exact algorithm varies, either one or both values can be used by it. This ....
Henning, M., Vinoski, S. (1999): "Advanced CORBA Programming with C++"; Addison-Wesley Longman
....is a fundamental aspect of the JTRS system architecture. CORBA is used to provide a cross platform middleware service that simplifies standardized client server operations in this distributed environment by hiding the actual communication mechanisms under an Object Request Broker software bus [24, 25]. CORBA is the Object Management Group s open architecture that provides the infrastructure for computer applications to work together over a network. A CORBA based application written in almost any language and running on almost any platform can interoperate with another CORBA based application ....
M. Henning and S. Vinoski. Advanced CORBA Programming with C++. Addison-Wesley, 1999.
....business operations and to communicate with others. Web Services [12] a joint effort by IBM, Microsoft and many others, is about making programmable application logics accessible using standard Internet Protocol. Its aim is similar to that of component technologies such as DCOM [22] or CORBA [11] but without the object model specific protocols. Instead, HTTP [4] and XML [6] are used. The Open Pluggable Edge Services (OPES) 3] are services that would be deployed in the network, i.e. at a web proxy cache between the origin server and the client, that would transform and or filter content. ....
M. Henning and S. Vinoski, Advanced CORBA Programming with C++, Addison-Wesley, 1999.
....such as for example, required operating system, and hardware platform. The specialization mechanism uses the requirements to query the active space infrastructure to obtain a list of matching entities. The syntax for the requirements is currently based on the CORBA s Trading Service query language [13]. The entry for the controller is optional, and in most cases is not used because presentations automatically register default controllers (this is the case of the example listed in Figure 5) 10 Model ClassName JukeboxModel Params f files location Cardinality 1 1 Requirements ....
M. Henning and S. Vinosky, Advanced CORBA Programming with C++: Addison-Wesley, 1999.
....two communication endpoints and the nodes must exchange information about the port address of each endpoint. To exchange between the endpoints, a special listening port exists on the server side. The server publishes its node identifier and port number of the listening port via an IOR profile [3]. In this profile, the node identifier replaces the host name. Therefore, the creation of an IOR profile for our CAN protocol is similar to IIOP and the changes to the code of ROFES are minimal. With use of this profile, the client can evaluate the listening port number and the node ....
....as 32 bit integer. In CANIOP, the method name is represented by a hash number. This hash number is calculated by a collision free hash function, which is created by the idl compiler for each interface. struct GIOPRequestHeader 1 2 unsigned long request id; octet response flag; octet reserved[3]; TargetAddress target; string operation; ServiceContextList svc ctxt; struct CANIOPRequestHeader unsigned long request id; octet response flag; TargetAddress target; unsigned long operation; ServiceContextList svc ctxt; Figure 6. Structure of the Request Message in GIOP and ....
M. Henning and S. Vinoski. Advanced CORBA Programming with C++. Addison-Wesley, 1999.
....into a file or a database. Even after being stringified and de stringified , it can be used to make requests on the object as long as the object still exists. 2.7.3 Object Adapters Architecturally, Object Adapters (OAs) serve as the interface between servants and the ORB. The term servant [61] refers to the programming language entity that implements one or more CORBA objects. Servants exist within the context of a server application ( a process implementing one or more operations on one or more objects [121] which bootstraps the ORB and the servant implementations. The term CORBA ....
....In addition, only objects that are incarnated (i.e. implemented) by an actual servant instance are capable of receiving and carrying out requests (servants can also be etherealised to break the bond with its CORBA object) Figure 2. 6 illustrates the di#erence between these concepts [61]. In the POA architecture, the lifecycles of objects and their servants do not have to correspond (i.e. the existence of an activated object and its reference does not mean that its servant is incarnated) It is possible that many objects share a single servant, or that one object is associated ....
[Article contains additional citation context not shown here]
M. Henning and S. Vinoski. Advanced CORBA Programming with C++. AddisonWesley, Reading, MA, 1999. 130
.... The growing use of middleware provides a more powerful distributed computing model that enables clients to invoke operations on reusable components without hard coding dependencies on their location, programming language, OS platform, communication protocols and interconnects, and hardware [10]. However, middleware (particularly standards based middleware) often has many features that are not needed by all applications that use it. For example, in the context of CORBA: A server application may not actually use all three versions (i.e. version 1.0, 1.1 and 1.2) of the standard CORBA ....
M. Henning and S. Vinoski, Advanced CORBA Programming With C++. Reading, Massachusetts: Addison-Wesley, 1999.
....systems, and supervisory control and data acquisition (SCADA) systems. CORBA is a DOC middleware standard defined by the Object Management Group (OMG) that allows clients to invoke operations on remote objects without concern for where the objects reside or what language the objects are written in [2]. In addition, CORBA shields applications from non portable details related to the OS hardware platform they run on or the communication protocols and networks used to interconnect distributed objects. These features make CORBA well suited to provide the core communication infrastructure for DRE ....
Michi Henning and Steve Vinoski, Advanced CORBA Programming with C++, Addison-Wesley, Reading, MA, 1999.
No context found.
M. Henning and S. Vinoski. Advanced CORBA Programming with C++. AddisonWestley, 1999. ISBN: 0-201-37927-9.
No context found.
Henning, M., Vinoski, S.: Advanced CORBA Programming with C++. Addison Wesley Longman, Inc. (1999)
No context found.
M. Henning and S. Vinoski. Advanced CORBA Programming with C++, volume 1 of Professional Computational Series. Addision-Wesley, 1 edition, April 1999.
No context found.
Michi Henning and Steve Vinoski. Advanced CORBA Programming with C++, chapter 19, pages 827-921. Addison Wesley, 1999.
No context found.
Henning, M., Vinoski, S.: Advanced CORBA Programming with C++. Addison Wesley Longman, Inc. (1999)
No context found.
M. Henning and S. Vinoski, Advanced CORBA Programming With C++. Addison-Wesley Longman, 1999.
No context found.
M. Henning, S. Vinoski, \Advanced CORBA Programming with C++", Addison Wesley Professional Computing Series, 1999
No context found.
M. Henning and S. Vinoski, Advanced CORBA Programming with C++. Addison-Wesley, 1999.
No context found.
M. Henning and S. Vinoski, Advanced CORBA Programming with C++. AddisonWesley, 1999.
No context found.
M. Henning and S. Vinoski. Advanced CORBA Programming with C++. Addison-Wesley Longman, 1999.
No context found.
Henning, M. and Vinoski, S., Advanced CORBA Programming with C++, Addison Wesley, 1999.
No context found.
M. Henning and S. Vinoski. Advanced CORBA Programming with C++. Addison-Wesley, Reading, Massachusetts, 1999.
No context found.
Michi, H. and Vinoski, S. (1999). Advanced CORBA Programming with C++. Addison-Wesley Pub Co.
No context found.
M. Henning and S. Vinoski, Advanced CORBA Programming with C++. AddisonWesley Publishing Company (1999).
No context found.
Henning, M., Vinoski, S. (1999): "Advanced CORBA Programming with C++"; Addison-Wesley Longman
First 50 documents
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC