Object Management Group, 2004. The Common Object Request Broker Architecture, http://www.omg.org. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Making Middleware Communication Architecture Reconfigurable - Georgantas, Sacchetti.. (2003) (Correct)
....is ooeered by the middleware layer to an external layer, i.e. the application layer. This service is supported by the fundamental part of the middleware layer, which we call the middleware core. The EIS is the only service expected from a minimal middleware infrastructure. In the example of CORBA [8], the middleware core is represented by the ORB. Using the EIS, a client application object can communicate with a remote server object simply by object method invocation. A couple of specialized middleware core objects, called stub on the side of the client object and skeleton on the side of the ....
Object Management Group, Common Object Request Broker Architecture (CORBA/ IIOP), 3.0.2 ed., 2002.
GCF: a General Coupling Framework - Ford, Riley, Bane, Armstrong (2002) (1 citation) (Correct)
....Sea Ice Soil) 15] and PALM (Project D Assimilation par Logicel Multi methods) 16] are such well established climate couplers. Many systems are evolving which claim to provide some level of automatic framework coupling. These include CACTUS [17] CCA [18] ESMF [11] and incarnations of CORBA [19], DCOM [20] and EJB [21] The latter frameworks require models to undergo signi cant modi cations for them to be framework enabled. Furthermore, the resulting coupled model includes signi cant overhead in terms of, for example, inter ORB communication and support daemons. FUTURE WORK As noted ....
Object Management Group. Common object request broker architecture (corba/iiop). OMG Speci cation.
DisCo: A Distribution Infrastructure for Securely.. - Freudenthal.. (2001) (Correct)
....and packaged solutions address different subsets of the problem of partly trusted environments, but these solutions are not well integrated. No one solution addresses the problem of decomposable applications in untrusted environments as a whole. Distributed component technologies like CORBA [11] and J2EE [18] have authorization models that do not respond well to dynamic changes in trust structure, and peer to peer protocols like JXTA [15] have not thus far included decomposed, heterogeneous components in its service delivery model. The DisCo infrastructure is intended to make the work ....
....that has been deployed on a host that was initially trusted, if at a subsequent time its trust level decreases. One application model that can satisfy this requirement is exemplified by several componentbased frameworks such as Sun Microsystems J2EE [18] Object Management Group s CORBA [11], and Microsoft s .NET [12] Applications in such frameworks are constructed out of multiple, interconnected components. Application deployment corresponds to mapping the components on a distributed network of hosts. An important characteristic of such decomposable applications is that the ....
[Article contains additional citation context not shown here]
Object Management Group. Common Object Request Broker Architecture (CORBA) Specification Version 2.5. Available at http://www.omg.org/technology/ documents/formal/corba_iiop.htm, 2001.
Access Policies for Middleware - Lang (2003) (2 citations) (Correct)
....was implemented as part of MICOSec [104] a level 2 conformant Open Source implementation of the CORBA security services v1.7 [121] MICOSec runs with MICO [103] a freely available and CORBA compliant (OpenGroup Open Brand for CORBA [128] implementation of the CORBA 2. 3 standard [118]. MICO only uses the standard Unix API (i.e. does not rely on proprietary or specialised libraries) and has a modular design even for implementation internals to ensure easy extensibility. MICOSec uses the Secure Sockets Layer Transport Layer Security (SSL TLS) 32] protocol as its underlying ....
Object Management Group. Common Object Request Broker Architecture, v2.3. Needham, MA, 2000. (document: formal/98-12-01).
Design for Change: Evolving Workflow Specifications in.. - Fent, Reiter, Freitag (2001) (Correct)
....in this paper the method to update and control access to specifications is presented in the context of afMS, it can also be applied in other situations where parts of a (possibly long running) program have to be exchanged on the fly. This happens in application servers for, e.g. CORBA [20]orEnterprise Java Bean (EJB) applications [25] when new versions of the program code are deployed and integrated into the system. This is frequently referred to as hot deployment . e performed some tests with Apache Tomcat [2]whichcan be seen as a minimal application server. Today, this ....
Object Management Group. The Common Object Request Broker Architecture, v2.0, 1997. http://www.omg.org. 518
A Framework for Inter Society Communication in Agents - Abbasi, Mitchell, Greenwood (2002) (Correct)
....in the same way that there is a need for different distributed object systems, written in different programming languages to communicate, it is becoming increasingly apparent that there is a need for different agent societies, with different communication methods, to be able to communicate. CORBA [3] and SOAP [27] are possible solutions for distributed objects, but due to the differences between objects and agents, they are currently unsuited for the challenges posed by Inter Society Communication (ISC) What is needed is a CORBA like solution for agent societies. 3 The Framework. There are ....
Common Object Request Broker Architecture (CORBA), Homepage: http://www.corba.org/ (2002)
$\chi$-Spaces: From a model to a working language - Caccamo, Crazzolara, Milicia (Correct)
....Alice tries to take the message from the tuple space using pattern matching. The message should contain enough redundancy so that Alice is able to choose the right message this issue is left entirely to the protocol and is not hardwired into SPL itself. In SPL messages are treated as persistent objects. Once sent on the network they are never removed. Informally process actions have the following meaning: new(x) p This process choses a value at random from some large set of basic values. Such value, say n is likely to be new and unguessable. The value n is bound to the variable x and when ....
....The main goal of # Spaces is to provide a uniform framework to design, verify and execute security protocols. In order to achieve the latter the user should be able to somehow integrate a protocol written in # Spaces into existing software. 20 On this regard we follow the approach taken by corba [Obj] Basically, the compiler for # Spaces programs takes a file containing the specification of a protocol, say MyProtocol.spl, and generates some files among then one defining a Java class, MyProtocol.java. This class extends the interface Protocol shipped in the standard distribution of # Spaces. ....
[Article contains additional citation context not shown here]
Object Management Group. Common Object Request Broker Architecture (CORBA/IIOP). Version 2.6.
Journal of Computer Science 1 (1): 76-82, 2005 - Issn Science Publications (Correct)
No context found.
Object Management Group, 2004. The Common Object Request Broker Architecture, http://www.omg.org.
A Multi-agent Approach to Manage a Network of Mobile Agent Servers - Braun, al. (2005) (Correct)
No context found.
Object Management Group. The Common Object Request Broker Architecture, Rev. 2.2, February 1998.
A Multi-agent Approach to Manage a Network of Mobile Agent Servers - Braun, al. (2005) (Correct)
No context found.
Object Management Group. The Common Object Request Broker Architecture, Rev. 2.2, February 1998.
Towards Grid-Wide Modeling and Simulation - Xie, Teo, Cai, Turner (2005) (Correct)
No context found.
"Common object request broker architecture (corba)," 2004. [Online]. Available: http://www.omg.org/gettingstarted/corbafaq.htm
Self-adaptive Functional Testing of Services - Working In Continuously (Correct)
No context found.
Common Object Request Broker Architecture (CORBA/IIOP), formal/2004-03-12. Object Management Group, March 2004.
Automatic Verification of Component-Based Real-Time.. - Madl, Abdelwahed, Karsai (2004) (Correct)
No context found.
Object Management Group. Common Object Request Broker Architecture (CORBA/IIOP). 2002.
Requirements and Design for XML Messaging in the Mobile .. - Kangasharju, Lindholm, .. (2005) (Correct)
No context found.
Object Management Group, Needham, Massachusetts, USA. Common Object Request Broker Architecture (CORBA/IIOP), version 3.0.3, Mar. 2004.
A New Protection Model for Component-Based Operating Systems - Law (2001) (4 citations) (Correct)
No context found.
Object Management Group. CORBA | Common Object Request Broker Architecture. Technical report, OMG, 1999. http://www.omg.org/. 117
A Peer-to-Peer Architecture for Delivering Services - Kalogeraki, Pruyne, van.. (Correct)
No context found.
Object Management Group, The Common Object Request Broker Architecture, formal/99-10-07, Version 2.3.1, October 1999.
From Processes to Policies - Concepts for Large Scale Policy.. - Danciu, Kempter (Correct)
No context found.
Common Object Request Broker Architecture (CORBA/IIOP). Omg specification, Object Management Group, December 2002.
From Processes to Policies - Concepts For Large Scale Policy.. - Danciu, Kempter (2004) (Correct)
No context found.
Common Object Request Broker Architecture (CORBA/IIOP). Omg specification, Object Management Group, December 2002.
The State of the Art in Service-Oriented Computing and Design - Dijkman, al. (2003) (Correct)
No context found.
Object Management Group. Common Object Request Broker Architecture (CORBA/IIOP) 3.02. OMG Document formal/2002-12-06, December 2002.
SynchNet: A Petri Net Based Coordination Language for.. - Ziaei, Agha (Correct)
No context found.
Object Management Group. Common Object Request Broker Architecture. OMG, 1999.
A Peer-to-Peer Architecture for Delivering E-Services - Kalogeraki, al. (2001) (2 citations) (Correct)
No context found.
Object Management Group, The Common Object Request Broker Architecture, formal/99-10-07, Version 2.3.1, October 1999.
Spatial Policies for Sentient Mobile Applications - David Scott Alastair (2003) (Correct)
No context found.
Object Management Group. Common Object Request Broker Architecture (CORBA/IIOP), 1995.
Ubiquitous Access to Reconfigurable Hardware.. - Indrusiak, Lubitz.. (2003) (Correct)
No context found.
Object Management Group. Common Object Request Broker Architecture (CORBA). v. 3.0. 2002. http://www.omg.org
Towards Distributed Process Networks with CORBA - Amar, Boulet, Dekeyser (2002) (1 citation) (Correct)
No context found.
Object Management Group, Inc., editor. Common Object Request Broker Architecture (CORBA), Version 2.6. http://www.omg.org/ technology/documents/formal/corba_iiop.htm, December 2001.
D Objects Visualization for Remote Interactive Medical.. - Johan Montagnat Eduardo (Correct)
No context found.
Object Management Group. Common Object Request Broker Architecture, Version 2.5. In http://www.omg.org/, Sept. 2001.
First 50 documents Next 50
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