2000
DOI: 10.1007/978-3-540-45347-5_18
|View full text |Cite
|
Sign up to set email alerts
|

Monitoring-Based Dynamic Relocation of Components in FarGo

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2000
2000
2011
2011

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 9 publications
0
3
0
Order By: Relevance
“…In order to provide a lightweight Core that can run on small devices, some of the FarGo components were omitted in the Cores that run on the NLPCs, including the monitoring facility (outside the scope of this paper, see [3]) and all system complets (including the shell). The main additions to the original architecture of FarGo are the Disconnected Manager (DM, explained below), the DA-referencing layer and the DA API 3.…”
Section: Architecturementioning
confidence: 99%
See 1 more Smart Citation
“…In order to provide a lightweight Core that can run on small devices, some of the FarGo components were omitted in the Cores that run on the NLPCs, including the monitoring facility (outside the scope of this paper, see [3]) and all system complets (including the shell). The main additions to the original architecture of FarGo are the Disconnected Manager (DM, explained below), the DA-referencing layer and the DA API 3.…”
Section: Architecturementioning
confidence: 99%
“…In this paper we present FarGo-DA, which extends the FarGo mobile framework [5,6,3,1] with support for Disconnected Aware (DA) applications. FarGo-DA provides a programming model for specifying disconnected-aware policies as part of the application, using a simple API; it extends the FarGo compiler with translation rules from DA annotations into FarGo-DA system calls; and it provides an infrastructure that implements and carries out these system calls at runtime.…”
Section: Introductionmentioning
confidence: 99%
“…For example, in FarGo [15] this component is known as a core and in most systems separate runtimes are required to allow different applications to run independently, although this is not the case with MobJeX, which can run multiple applications in a single runtime using threads. The applications themselves comprise mobile objects, which interact with each other through proxies [14].…”
Section: Introductionmentioning
confidence: 99%