Dynamic Integration of Peer-to-Peer Services into a CORBA-Compliant Middleware

Kapitza, Rüdiger; Bartlang, Udo; Schmidt, Holger; Hauck, Franz J.

doi:10.1007/11915034_13

Cited by 5 publications

(4 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Based on this work, we developed a decentralised type of the DLS (P2P-DLS) [13,14]. This service allows any participating peer to offer and to obtain platform-specific code in a dynamic and heterogeneous environment.…”

Section: Dynamic Loading Of Codementioning

confidence: 99%

Mobile-process-based ubiquitous computing platform

Schmidt¹,

Kapitza

Hauck³

2007

Proceedings of the 1st Workshop on Middleware-Application Interaction in Conjunction With Euro-Sys 2007 - MAI '07

Self Cite

View full text Add to dashboard Cite

Mobile objects and agents are used for implementing distributed applications. Both concepts allow efficient use of local resources, volatile network connectivity and more efficient communication due to appropriate migration, especially in dynamic ubiquitous environments. Mobile processes enable specifying the complete life cycle of complex mobile applications. In this paper, we propose a mobile-process-based platform that turns ubiquitous application development into a manageable task. We advocate the use of Web services for implementing mobile processes in a heterogeneous environment. Based on previous work, we sketch a novel approach for realising mobile context-aware Web services, which implement process steps. We use a separation of state, functionality and implementation code, which enables a reduction, expansion and transformation of the service state and functionality during migration.

show abstract

Section: Dynamic Loading Of Codementioning

confidence: 99%

Mobile-process-based ubiquitous computing platform

Schmidt¹,

Kapitza

Hauck³

2007

Proceedings of the 1st Workshop on Middleware-Application Interaction in Conjunction With Euro-Sys 2007 - MAI '07

Self Cite

View full text Add to dashboard Cite

show abstract

“…In [10,24], we proposed an extension to the DLS using a P2P-based infrastructure to solve issues of server-based solutions. In contrast to this approach, our current work provides filtering mechanisms in the network, automatically resolves dependencies, and is transparently integrated as a service into OSGi.…”

Section: Related Workmentioning

confidence: 99%

OSGi 4C

Schmidt¹,

Elsholz²,

Nikolov³

et al. 2009

Proceedings of the Fourth International ICST Conference on COMmunication System softWAre and middlewaRE

Self Cite

View full text Add to dashboard Cite

OSGi is an industry standard for a lean Java-based component system with focus on local applications following the service-oriented architecture. Initially developed for dedicated application domains such as gateways and set-top boxes it is meanwhile used in many other areas, with Eclipse as a prominent example. OSGi allows dynamic deployment of components called bundles with automatic local dependency resolution on basis of exported Java packages. In this regard, OSGi builds an ideal basis for demand-driven deployment of complex Java applications, such as needed in the context of emerging cloud computing infrastructures. However, it lacks distributed code deployment and resolving.We present OSGi for the Cloud (OSGi4C ), a novel OSGi service allowing seamless deployment of locally non-existent OSGi bundles and services on demand without requiring any changes to the OSGi platform. In OSGi4C , we use an underlying peer-to-peer infrastructure to provide, share and load OSGi bundles at runtime. Unlike related work, OSGi4C automatically resolves OSGi bundle and service dependencies. Therefore, dependent bundles that are not yet locally installed are also deployed. OSGi4C considers platform-specific implementations (e.g., native code) and non-functional requirements (e.g., performance and resource demand) while automatically discovering and selecting the best of multiple available bundles for download.

show abstract

“…This step results in an IOR other Aspectix systems can use for binding. If those systems cannot provide the necessary code, then Aspectix uses the Aspectix loading service that is peerto-peer based and completely transparent for users [19,20]. We argue that the lack of transparency during service initialisation is justified, because at least the owner of a service should know, whether the service runs replicated.…”

Section: Separating Aspectix and Ftflexmentioning

confidence: 99%

Towards generic and middleware-independent support for replicated, distributed objects

Domaschka

Reiser

Hauck

2007

Proceedings of the 1st Workshop on Middleware-Application Interaction in Conjunction With Euro-Sys 2007 - MAI '07

Self Cite

View full text Add to dashboard Cite

Replication is a commonly used approach to increase the availability of distributed services, which is a non-functional requirement. Thus, replication is in principle independent of the application logic. For this reason, support for replication is part of middleware architectures. Each of them provides its own replication infrastructure, although the differences in functionality are rather marginally. In this paper we claim that replication is even independent of the middleware the application uses. We propose a separation of concerns between middleware and replication systems and present a generic architecture that allows the middleware to support replication by using an existing replication framework. We argue that such an approach is equally transparent, but less intrusive than existing approaches. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. MAI '07, March 20, 2007, Lisbon, Portugal Copyright 2007/07/0003 ...$5.00. Categories and Subject Descriptors MOTIVATIONAvailability is a non-functional requirement of many applications. Replication is one way to provide availability. Thus, it is independent of the application logic. For this reason, support for replication is part of middleware architectures, such as CORBA. Each of them provides its own replication infrastructure, but the basic procedure is always identical. A client request is forwarded to multiple or even the entire group of replicas respecting a consistency model.Integrating replication support directly into the middleware systems has several drawbacks. First of all, it bloats up the middleware code, though not all applications make use of it. Second, mixing up code for middleware tasks such as referencing and binding with code for logic concerning nonfunctional and sometimes cross-cutting requirements such as those for replication, QoS, or fault-tolerance introduces a coupling between multiple in principle unrelated software modules leading to code that is difficult to debug, maintain, change, and extend. Thus, replication logic should be separated from the middleware core.In this paper we claim, that replication is independent of the concrete middleware architecture with respect to distributed objects. Those middleware systems should be able to re-use existing replication frameworks to prevent reinventing the wheel for every new middleware system. Having an open framework architecture, enables to add additional replication-related issues, such as a new replication strategy or optimisations, for all middleware systems at one go. Finally, development costs for middleware systems are decreased and the development cycle is shortened.We present a generic architecture that allows a mid...

show abstract

Dynamic Integration of Peer-to-Peer Services into a CORBA-Compliant Middleware

Cited by 5 publications

References 3 publications

Mobile-process-based ubiquitous computing platform

Mobile-process-based ubiquitous computing platform

OSGi 4C

Towards generic and middleware-independent support for replicated, distributed objects

Contact Info

Product

Resources

About