OMG, "CORBAservices: Common Object Services Specification", Updated Revision 2.1, November 1997 Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents
Implementing Dynamic Load Distribution Strategies with Orbix - Schnekenburger (1997) (1 citation) (Correct)
....migration, trading, Orbix, CORBA 1 Introduction CORBA [4] is currently the most important commercial programming standard for distributed systems. In contrast to academic platforms for parallel computing in distributed sys tems such as PVM [9] and Linda [2] CORBA defines several basic services [5] (such as for ex ample a naming service, persistent object ser vice, transaction service, etc. Therefore it The research described in this paper was performed while T. Schnekenburger was at the Institut ffir Informatik, Technische Universitt Mtinchen. It was sup ported in part by the DFG ....
OMG (Object Management Group), "CORBAservices: Common Object Services Specification", Technical Report 95-3-31, March 1995.
Load Management for Distributed Object-Oriented Environments - Lindermeier (2000) (7 citations) (Correct)
....Definitions In the previous section object replication as one load distribution mechanism was introduced. In general, all objects can be replicated but it may be necessary to take measures in order to keep the state of the replicas consistent. For example, when replicating a CORBA Naming Service[10] some kind of consistency protocol has to guarantee that a name that is registered at one replica is registered at the other replicas, too. Such consistency protocols may cause substantial communication or computation overhead. Furthermore, consistency protocols that can be implemented at system ....
....start the ORB s request handling. This approach is inapplicable to services that have to create objects on demand like load management or fault tolerance services. In general, activation issues, i.e. starting a process and creating objects, are unsolved in CORBA. Originally, the Life Cycle Service[10] was designed to manage activation and load distribution but there is no entire implementation available so far. One of the reasons might be the loose coupling between the Life Cycle Service on the one hand and the ORB and the POA on the other hand. This complicates the implementation or makes it ....
[Article contains additional citation context not shown here]
OMG (Object Management Group). CORBAServices: Common Object Services Specification. Technical report, http://www.omg.org, 1998.
Integrating SSL to the JaCoWeb Security Framework.. - Wangham, Lung.. (2001) (Correct)
....channel for distributed objects. In CORBA, interoperability among objects is obtained through the objects IDL (Interface Definition Language) specifications. In object oriented applications development, the CORBA standard offers an additional COSS (Common Object Service Specification) [5] that provides an easier application development. These services are OMG standards within the OMA (Object Management Architecture) perspective. These service objects form a collection of services (interfaces) at the system level, and offer basic functionality for usage and implementation of ....
....an application selects the connection mode to be used (secure or conventional) In the CORBA model, an object can be located in the distributed system through its object references. In the OMG, these object references are defined by the IOR specification (Interoperable Object Reference) The IOR [5] is a character sequence which, when converted to proper formats, supplies information such as the port, the IP address, a pointer to the object to be accessed and some IOR specific control data. The CORBASec specification defines an IOR extension in order to be able to gather specific information ....
[Article contains additional citation context not shown here]
OMG, "CORBAservices: Common Object Services Specification", 1997.
High Availability Support for Distributed Object Systems - Galdámez.. (Correct)
....D.4.7 [Operating Systems] Organization and Design distributed systems General Terms: Distributed systems, Object Oriented Applications, Reliability Additional Key Words and Phrases: Distributed algorithms, group communication, high availability, fault tolerance, CORBA 1. INTRODUCTION CORBA [OMG 1995a] is a good basis to develop object oriented distributed applications. Its central component is the object request broker (ORB) which provides the means needed to deal with object invocations and responses in distributed environments, even in heterogeneous ones. The architecture also enables ....
....to deal with object invocations and responses in distributed environments, even in heterogeneous ones. The architecture also enables the development of these objects in different programming languages, providing the appropriate maps from its interface definition language. Several object services [OMG 1995b] have been added to the basic ORB specification, including support for naming, persistence, security, relationships, transactions, concurrency control and so forth. All these services assist the programmer in the development tasks, providing additional characteristics to the resulting ....
OMG. 1995b. CORBAservices: Common Object Services Specification. Object Management Group. Revised Edition.
TRIP: A Distributed vision-based Sensor System - de Ipina (1999) (1 citation) (Correct)
....and networks used to interconnect distributed objects. Client and server objects may exist within the same machine or on different machines. An object reference is an identifier that uniquely specifies an object within a distributed ORB system. The CORBA Common Object Services (COS) specified at [OMG98b] are architectural models and interfaces that factor out common services for developing distributed applications. In this work the Naming Service and specially the Event Service are employed. The OMG Naming Service is the principal mechanism for objects on an ORB to locate other objects. The ....
....registered consumer object references to perform a distributed callback every time an event had to be transmitted. However, the OMG Event Service used presents some notorious deficiencies as it has been well described in [Smith97] The first one is that the OMG Event Service specification [OMG98b] does not define requirements for some key Event Channel characteristics, and therefore the quality of service provided by Event Channels varies widely with the implementation. Some implementations employ unicast for event transmission whereas more efficient ones utilise multicast instead. ....
OMG, Object Management Group, "CORBA Services: Common Object Services Specification", September 1998, ftp://ftp.omg.org/pub/docs/formal/98-12-09.pdf
Building Components for a Distributed Sentient Framework with.. - de Ipina (2000) (Correct)
....without the components knowing about each other. OMG s CORBA [9] is the chosen middleware because of its platform and language inter operability features, its popularity as an open standard for component software operation and its rich set of standard distributed services. The CORBA Event Service [10] is used to enable SIF components to asynchronously notify contextual events, to interested applications or other SIF components, through Event Service s Event Channels (renamed as Context Channels in SIF) If the Event Service had not been used, each SIF component would have had to perform a ....
....create object in this factory to generate the TRIP Directory Server Context Channel and connects to it as a push event supplier. Figure 7 shows how this registration process is implemented in Python. It might prove a little difficult to understand without a thorough study of the OMG Event Service [10]. When the TRIP Directory Server s shelves are modified, a notification is pushed to the previously obtained channel indicating the type and attributes of the modification. Figure 8 shows the Python code for sending a TRIPcode creation notification (AddTRIPcodeEvent IDL structure in Figure 6) ....
[Article contains additional citation context not shown here]
OMG, Object Management Group, "CORBA Services: Common Object Services Specification", September 1998, ftp://ftp.omg.org/pub/docs/formal/9812 -09.pdf
Design Patterns for Description-Driven Systems - Le Goff, Willers (1999) (Correct)
....4.4 Meta Objects and Standardisation In distributed object based systems, object request brokers provide for the exchange of simple data types and, in addition, provide location and access services. The CORBA standard is meant to standardise how systems interoperate. OMG s CORBA Services [10] specify how distributed objects should participate and provide services such as naming, persistent storage, life cycle, transaction, relationship and query. The CORBA Services standard is an example of how self describing software components can interact to provide interoperable systems. Recently ....
OMG, "CORBAservices: Common Object Services Specification". OMG publications, 1994.
A Framework for Systematic Synthesis of Transactional.. - Apostolos Zarras Val (1998) (7 citations) (Correct)
....systems vary a lot and the transaction concept had to adapt with respect to them. As a result, a variety of transaction models [11, 14] were developed in order to deal with the newly imposed requirements (e.g. performance, cooperation) Moreover, some well known processing standards (e.g. CORBA [13], ODP [16] include the specification of services that provide transactional properties (e.g. locking, persistence, recovery) However, to ascertain whether or not some required transactional properties are supported by existing standard services is a tedious task. For instance, let us consider ....
....generated during the composing procedure, together with the stub code for the deposit( and withdraw( operations. Middleware Synthesis Two standard CORBA Common Object Services can be used to synthesize a middleware that conforms to the banking system requirements. The OTS service (chapter 10 in [13]) provides the global atomicity property through a distributed commitment protocol, while the CCS service (chapter 7 in [13] is associated with two phase and well formed locking. Given the behavior of two phase and well formed locking, it can be formally proved that they imply an isolated ....
[Article contains additional citation context not shown here]
OMG Document. CORBAservices: Common Object Services Specification. Technical report, Object Management Group, 1995.
A Framework for Systematic Synthesis of Transactional Middleware - Zarras, Issarny (1998) (7 citations) (Correct)
....vary a lot and the transaction concept had to adapt with respect to them. As a result, a variety of transaction models [15, 19, 7, 17] were developed in order to deal with the newly imposed requirements (e.g. performance, cooperation) Moreover, some well known processing standards (e.g. Corba [18], Odp [21] include the specification of services that provide transactional properties (e.g. locking, persistence, recovery) However, to ascertain whether or not some required transactional properties are supported by existing standard services is a tedious task. For instance, let us consider ....
....during the composing procedure, together with the stub code for the deposit( and withdraw( operations. 3.2 Middleware Synthesis Two standard Corba Common Object Services can be used to synthesize a middleware that conforms to the banking system requirements. The Ots service (chapter 10 in [18]) provides the flat property through a distributed commitment protocol, while the Ccs service (chapter 7 in 11 COMPONENT BankClient f SOURCE: xxx BANKclient i.cc; PLATFORM: MIDDLEWARE = CORBA; LANGUAGE = C ; EXCEPTIONS: InsufficientFunds fg; IMPORTS: VOID withdraw(IN FLOAT balance) RAISES ....
[Article contains additional citation context not shown here]
OMG Document. CORBAservices: Common Object Services Specification. Technical report, Object Management Group, 1995.
Dynamic Server Selection In Distributed Object Computing.. - Badidi, Keller, Kropf.. (Correct)
....OMG, the naming service (or directory service) and the trading service, allow locating objects in a distributed object system. The naming service is a mechanism which makes it possible for the objects of a distributed application to locate other objects (local or remote) by means of their names [12]. The names are humanly recognizable values associated with an object. An object is identified by means of a reference object (i.e. an internal structure of identification that contains a fixed set of fields) The resolution of a name consists in determining the reference object associated with ....
OMG: "CORBAservices: Common Object Services Specification".- Updated version: July (1997).
Engineering Access Control for Distributed Enterprise Applications - Beznosov (2000) (4 citations) (Correct)
....flexibility lacking from other paradigms in this direction, such as Legion (Section 3.2.2.4) In particular, it allows attaching multiple SMOs to the same object reference so that several policies or additional functionalities can be composed. This is very similar to CORBA request interceptors [OMG 1996a] which are invoked before an invocation is scheduled on an interface implementation by the ORB or before it is prepared to be sent to another CORBA object. However, SMOs are attached to an object reference. Whereas, CORBA interceptors are attached to an instance of an interface ....
OMG, "CORBAservices: Common Object Services Specification," Object Management Group, 1996.
Monitoring and Controlling Operations - Jones, Yih, Wallace (2000) (Correct)
....(MIES) software (Doscher 1998) the following material is taken largely from (Hawker 1999) The CIM framework is not hierarchical in nature; rather, it leverages distributed, object oriented computing technology. Additionally, it uses middle ware standards from the Object Management Group (OMG) http: www.omg.org) to enable integration of the applications. The CIM Framework software architecture was designed to enable the following capabilities: Integration applications can cooperate by exchanging data, providing services (client server method invocation) publishing service ....
....(Doscher 1998) the following material is taken largely from (Hawker 1999) The CIM framework is not hierarchical in nature; rather, it leverages distributed, object oriented computing technology. Additionally, it uses middle ware standards from the Object Management Group (OMG) http: www. omg.org) to enable integration of the applications. The CIM Framework software architecture was designed to enable the following capabilities: Integration applications can cooperate by exchanging data, providing services (client server method invocation) publishing service exceptions, and ....
[Article contains additional citation context not shown here]
OMG (1996) CORBAservices: Common Object Services Specification. Object Management Group, Framingham, Massachusetts.
The Design and Performance of a CORBA Audio/Video.. - Mungee, Surendran, .. (1999) (13 citations) (Correct)
....Media (UDP) ######## ######## ######## ######## ######## ######## ####### ####### Figure 16: Architecture of the MPEG A V Streaming Application The MPEG player application uses a supplier consumer design implemented using TAO. The consumer locates the supplier using the CORBA Naming Service [OMG, 1997b] or the Trading Service [OMG, 1997b] to find suppliers that match the consumer s requirements. For instance, a consumer might want to locate a supplier that has a particular movie or a supplier with the least number of consumers currently connected to it. Once a consumer obtains the supplier s ....
....######## ######## ######## ####### ####### Figure 16: Architecture of the MPEG A V Streaming Application The MPEG player application uses a supplier consumer design implemented using TAO. The consumer locates the supplier using the CORBA Naming Service [OMG, 1997b] or the Trading Service [OMG, 1997b] to find suppliers that match the consumer s requirements. For instance, a consumer might want to locate a supplier that has a particular movie or a supplier with the least number of consumers currently connected to it. Once a consumer obtains the supplier s MMDevice object reference it requests ....
OMG (1997b). CORBAServices: Common Object Services Specification, Revised Edition. Object Management Group, 97-12-02 edition.
Transactions In Transactional Workflows - Worah, Sheth (9 citations) (Correct)
.... hand, provide more open and cost effective solutions for implementing large scale distributed workflow applications [Sheth et al. 1996b, Palaniswami et al. 1996] In partic TRANSACTIONS IN TRANSACTIONAL WORKFLOWS 21 ular, the CORBA standard [OMG, 1995b] includes specifications for services [OMG, 1995a] such as the Object Transaction Service (OTS) the Concurrency Control Service, and the Persistence Service that can be combined to form a framework for achieving TP monitor like functionality in a HAD environments. 1.6.1 Error Handling and Recovery in the METEOR 2 WFMS The study of workflow ....
....(as in secure transactions supported in the electronic commerce and Web based services) The concept of transactions has been addressed in many of these technologies to some extent. For example CORBA provides an Object Transaction Service as a part of the CommonObject Services Specification [OMG, 1995a] that enables objects in distributed environments to take part in a transactional context; TP monitors also provide transactional semantics in a distributed environment. The HTTP protocol used in the Web paradigm, on the other hand, does not provide any transactional semantics. Hence, we see ....
OMG (1995a). CORBAservices: Common Object Services Specification. Technical report, Object Management Group.
Trading Service - Cooperative Research Centre (Correct)
....Language for Expressions At a minimum, the expression language should support: property names and constant values . comparison operators (e.g. logical connectives (e.g. and, or, not) normal precedence and grouping (e.g. as described in Appendix 5B of the Life Cycle Service [4]. However, this minimal constraint language is limited to expressions involving strings and numeric types. Since property types can include all the basic types and the user defined types (due to the use of CORBA any) some implementations of the ServiceOffer interface might choose to support an ....
....does not include a naming mechanism for traders or service types, as this functionality is already available through the Naming Service. Similarly, this specification does not include a graph mechanism for links as this functionality is already available through the Relationship Service [4]. No hidden interfaces among object services This Trading Service specification does not require any hidden interfaces. Consistency among object services This Trading Service specification is designed to be consistent in approach and style with other object services, e.g. the use of iterators ....
[Article contains additional citation context not shown here]
OMG, "CORBAservices: Common Object Services Specification", OMG TC Document Number 95.3.31, March 1995.
Standards Project: - Operations Administration Maintenance (Correct)
....interfaces where Rec. Q.812 is updated with protocol profiles using CORBA for different interfaces. 3 CORBA Common Object Services Recommendations The CORBA ORB provides basic object to object interaction capabilities. 1] Additional capabilities are defined as separate, Common Object Services. [2] The CORBA Common Object Services are general purpose, domain independent services that are fundamental for developing CORBA applications composed of distributed objects. They also provide the basic building blocks for application interoperability. The services are defined with object interfaces ....
....of CORBA for network management. The following sub sections specify recommendations on the use of CORBA Common Object Services to ensure interoperability between different network management systems. 3.1 The Naming Service The OMG Naming Service is CORBA s directory service, or white pages. [2] It allows a client to build a name to object association called a name binding that other clients can then use to find the object. CORBA object addresses can be long and difficult for use by humans. A name binding is always defined relative to a naming context. A naming context is an object ....
[Article contains additional citation context not shown here]
OMG, "CORBAservices: Common Object Services Specification", Updated version, December 1998.
Towards Monitoring in Parallel and Distributed Environments - Zoraja, Rackl, Ludwig (1999) (1 citation) (Correct)
....remote procedure calls. The DOC functionality is provided by means of services offered by servers and implemented as objects which are distributed across a pool of servers. Services are described by defining interfaces using an interface definition language (IDL) Typical representatives are CORBA [6, 7], DCOM [10] and Java RMI [13] A detailed discussion on DSMs and DOCs can be found in [17] 3 3 Monitoring Issues Monitoring systems connect parallel tools to running applications. According to Figure 1, softwarebased monitoring systems have the same structure as other parallel and distributed ....
OMG (Object Management Group). CORBAservices: Common Object Services Specification. Technical report, November 1997.
Customer Facing Components for Network Management Systems - Busse, Covaci (1997) (1 citation) (Correct)
....a relation object. In such a case a new copy operation has to be provided that takes care of the relation graph and traverses it. Whether a referenced object will be copied or not is decided based on the attributes of the relation. This approach is taken in the COSCompoundLifeCycleService of Corba [COS]. It might be helpful to have a similar service in our environment. A very important issue is security. Currently there are security restrictions neither at the remote interface for creating agents nor at the remote interface for retrieving classes. If the environment should be opened to a public ....
OMG: "CORBAservices: Common Object Services Specification", Revision 1.0, March 1995.
Unknown - Ikv National Technical (Correct)
No context found.
OMG, "CORBAservices: Common Object Services Specification", Updated Revision 2.1, November 1997
Object Security Attributes: Enabling Application-specific Access .. - Beznosov (2002) (2 citations) (Correct)
No context found.
OMG, "CORBAservices: Common Object Services Specification, Security Service Specification v1.7," document formal/01-03-08 2001, http://www.omg.org/cgi-bin/doc?formal /01-03-08.
Integration of Mobile Agent Technology into Intelligent.. - ZIZZA, BREUGST, al. (Correct)
No context found.
OMG, "CORBAservices: Common Object Services Specification", Updated Revision 2.1, November 1997
An enhanced CCE event manager - Messina Pleinevaux Swiss (Correct)
No context found.
OMG, "CORBA Services: Common Object Services Specification", OMG Mar, 1995.
Distribution To: - Standards Project Protocol (Correct)
No context found.
OMG; "CORBAservices: Common Object Services Specification; March, 1995; http://www.omg.org/library/csindx.html
An Application-oriented System for Quality of Service.. - Tsaoussidis, Deka.. (Correct)
No context found.
OMG, "CORBA Services: Common Object Services Specification", Trading Object Service Specification v1.0, March 1997.
DCE/CORBA Interworking Service - Submitted By Cooperative (Correct)
No context found.
OMG, "CORBAservices: Common Object Services Specification", OMG TC Document Number 95.3.31, March 1995.
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