Distributed Object
Przemysław Kazienko · 2008
Cited by 0
Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “Distributed object”
Przemysław Kazienko · 2008
Cited by 0
Güray Yılmaz · Istanbul Technical University Academic Open Archive (Istanbul Technical University) · 2002
Tez (Doktora) -- İstanbul Teknik Üniversitesi, Fen Bilimleri Enstitüsü, 2002
Cited by 0Open access
Bucher, Andrew Bryan, Young, Matthew D. · Digital WPI · 1999
Intellution Inc. provides software, which maps logical names to physical devices in a factory setting. Increasing factory complexity compounds the problem of managing these devices. We propose a distributed middleware solution, the Distributed Object Brokerage, which manages the mappings between logical names and physical devices in a factory. This paper explores the design considerations necessary to implement such a system in an efficient and scalable manner. In addition a prototype was implemented to test the feasibility of the concepts presented.
Cited by 0
And Component Designs, Nima Kaveh, Wolfgang Emmerich · 2003
Cited by 0
Santosh N. Sreenivasan · Lehigh Preserve · 1997
A MPI examples B CORBA examples C DCOM examples
Cited by 0Open access
Wen Zhao · 1999
Distributed object technology is recently developed software technology based on object-orientation and supporting distributed applications, it implements object's interoperability in the heterogeneous environment. [
Cited by 0
Kathy Bobrer
The article focuses on the San Francisco project, a business process software for distributed object applications, which offers developers extendable components to simplify the transition to distributed, easily customizable applications. It was started when several business partners of the software company IBM Corp. asked for help in modernizing their application products which were typically written in procedural languages, such as RPG or Cobol. While most approaches to object-oriented design assume the result of the process as a finished application that is used in the operation of a business, the San Francisco project has a different design goal. It is not intended to be a finished application. It is rather, a starting point for an application developer and is intended to be modified. The design process was begun by capturing the requirements for the vertical domain that were being examined. Further, the San Francisco project is building three layers of reusable code for use by application developers with the top layer consisting of business process components for key business activities, the second providing definitions of commonly used business objects that can be used as the base for interoperability between applications, and the third layer provides the infrastructure and services required to build industrial-strength applications using distributed, managed objects on multiple platforms.
Cited by 0
Frank Manola, Sandra Heiler, Dimitrios Georgakopoulos et al. · International Journal of Cooperative Information Systems · 1992
Future information processing environments will consist of a vast network of heterogeneous, autonomous, and distributed computing resources, including computers (from mainframe to personal), information-intensive applications, and data (files and databases). A key challenge in this environment is providing capabilities for combining this varied collection of resources into an integrated distributed system, allowing resources to be flexibly combined, and their activities coordinated, to address challenging new information processing requirements. In this paper, we describe the concept of distributed object management, and identify its role in the development of these open, interoperable systems. We identify the key aspects of system architectures supporting distributed object management, and describe specific elements of a distributed object management system being developed at GTE Laboratories.
Cited by 145
E. H. Bensley, Thomas J. Brando, J. C. Fohlin et al. · 1990
Abstract : This paper describes a concurrent model of execution for object oriented programming. In addition, it describes a computation manager that implements this model and a compiler that translates a subset of Common Lisp with Flavors object oriented extension to code executable by the computation manager. Finally, fault tolerant resources management algorithms and a simulation of a multiprocessor system that embodies these algorithms are described.
Cited by 1
Paulo Guedes, Miguel Castro · 2002
This paper describes the goals, programming model and design of DiSOM, a software based distributed shared memory system for a multicomputer composed of heterogeneous nodes connected by a high-speed network. A typical configuration is a cluster of tens of high-performance workstations and shared-memory multiprocessors of two or three different architectures, each with a processing power of a few hundred MIPS and several hundred kilobytes of memory, and connected by a high-speed interconnect such as ATM. Programs in DiSOM are written using a shared-memory multiprocessor model where synchronization objects are associated with data items. Programs use a threads library to start new threads, possibly at a specified node, and to synchronize between concurrent threads. Programs must call the synchronization primitives explicitly, as they would in a shared-memory multiprocessor. The system traps these calls and uses the information to drive both distributed synchronization and the memory coherence protocol. DiSOM uses the entry consistency memory model to ensure coherence. This model guarantees memory consistency, as long as an access to a data item is enclosed between an acquire and a release on the synchronization object associated with the data item. Stronger consistency models, such as release consistency and processor consistency, may also be supported.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
Cited by 21
Letha H. Etzkorn · 2017
Cited by 0
Vijay Varadharajan · IFIP advances in information and communication technology · 1995
Cited by 6Open access
Bærbak Christensen, Bærbak Christensen · 2015
Cited by 0
John Scourias University, John Scourias · 2007
The increasingly widespread implementation of distributed systems is a well established trend, due to the many benefits provided by distributed client-server systems over centralized systems, such as application and data sharing, reliability and better price/performance ratios. The implementation of distributed systems is, however, a difficult task, and the computer industry is relatively inexperienced in handling the complexity encountered. The object-oriented paradigm provides an inherent abstraction mechanism that can be used to hide much of this complexity. The Object Management Group&apos;s Common Object Request Broker Architecture (CORBA) is a recent specification for an Object Request Broker, the mechanism that allows requests to be issued and replies received transparently in a heterogeneous distributed system. The Object Management Group&apos;s design for a distributed object management system, including CORBA, will be discussed, as well as some proposals for the next revi...
Cited by 0
Harry H. Porter, Earl F. Ecklund, Denise J. Ecklund et al. · Lecture notes in computer science · 1988
Cited by 3
E. D’Azevedo, C.H. Romine · OSTI OAI (U.S. Department of Energy Office of Scientific and Technical Information) · 1994
This report describes the use and implementation of DOLIB (Distributed Object Library), a library of routines that emulates global or virtual shared memory on Intel multiprocessor systems. Access to a distributed global array is through explicit calls to gather and scatter. Advantages of using DOLIB include: dynamic allocation and freeing of huge (gigabyte) distributed arrays, both C and FORTRAN callable interfaces, and the ability to mix shared-memory and message-passing programming models for ease of use and optimal performance. DOLIB is independent of language and compiler extensions and requires no special operating system support. DOLIB also supports automatic caching of read-only data for high performance. The virtual shared memory support provided in DOLIB is well suited for implementing Lagrangian particle tracking techniques. We have also used DOLIB to create DONIO (Distributed Object Network I/O Library), which obtains over a 10-fold improvement in disk I/O performance on the Intel Paragon.
Cited by 4Open access
Programming Droop Eugster, P. Eugster · 2007
The Simple Object-Oriented Concurrent Programming (SCOOP) model proposed by Bertrand Meyer and illustrated through the Ei#el programming language is a simple yet powerful model for concurrent programming.
Cited by 0
Z. George Mou · Lecture notes in computer science · 1999
Cited by 0
E. Marais, E. M. Ehlers, D. Dutta · 2008
This article discusses a model for creating distributed manufacturing resources by allowing each manufacturing resource to be represented as an object. The manufacturing resources discussed in this article are layered manufacturing machines but the model can be adapted for use with other machines/methods. The model allows a user to submit a design to layered manufacturing hardware directly. The components needed to allow direct submission are a processing server and a locating agent to allow the manufacturing resources to be used. Part of the model is to allow new manufacturing resources to be added to the distributed manufacturing resources. Thereby allowing a user without the capital to buy a layered manufacturing machine the advantages provided by them. By allowing access to this distributed pool of manufacturing resources the user can have access to more complex layered manufacturing machines than large organisations, with the added benefit of higher availability.
Cited by 0
Nikolay K. Diakov, Cover Design, Studio Oude Vrielink et al. · 1973
in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying,
Cited by 0