Proceedings Seventeenth IEEE Symposium on Reliable Distributed Systems (Cat. No.98CB36281)
DOI: 10.1109/reldis.1998.740480
|View full text |Cite
|
Sign up to set email alerts
|

A fault-tolerant protocol for providing the exactly-once property of mobile agents

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
50
0

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 52 publications
(50 citation statements)
references
References 21 publications
0
50
0
Order By: Relevance
“…When a worker fails, one of participants is elected as a new worker and takes over the action of the previous worker. To provide the exactly once property of a mobile agent execution, voting and agreement protocols are needed at each stage [7,3].In a multi-region mobile agent computing environment, places within a stage can be located in the same or different regions [7].…”
Section: E Region-based Stage Construction Protocolmentioning
confidence: 99%
See 1 more Smart Citation
“…When a worker fails, one of participants is elected as a new worker and takes over the action of the previous worker. To provide the exactly once property of a mobile agent execution, voting and agreement protocols are needed at each stage [7,3].In a multi-region mobile agent computing environment, places within a stage can be located in the same or different regions [7].…”
Section: E Region-based Stage Construction Protocolmentioning
confidence: 99%
“…Non-blocking property ensures that the agent execution can make progress at any time and exactly-once execution property prohibits multiple executions of the agent. As many of mobile agent applications require an agent to be executed exactly once [3].…”
Section: Introductionmentioning
confidence: 99%
“…Table 2 presents the existing implementations of each study and the failure types designed for them. [25], [30], [31], [32], [42], [36], [38], [39], [43], [44], [45] [5], [7], [25], [26], [27], [29], [30], [31], [32], [34], [42], [35], [36], [38], [40], [41], [14], [44], [46], [47], [43], [45] [25], [26], [5], [27], [28], 29], [30], [31], [32], [33], [42], [7], [36], [38], [39], [40], [41], [44], [46], …”
Section: Srq2 What Available Fault Models Are Considered In Designinmentioning
confidence: 99%
“…Crash and agent software fault models seem to be supported in most of the existing implementations (84%). Only about 35% of the studies supported all three fault models [44], [27], [38], [30], [31], [32], [42], [36], [45], while 12% of these studies considered the issue of network partitioning and suggested a solution to it [44], [38], [30]. …”
Section: Srq2 What Available Fault Models Are Considered In Designinmentioning
confidence: 99%
“…Mobile agent technology has been applied for various application areas such as wired/wireless Internets management, and E-commerce [1] [3][4] [7][8] [11]. Mobile agents are autonomous objects that migrate from node to node of Internet and provide to user which have executed themselves using database or computation resources of clients connected by the wired/wireless Internets.…”
Section: Introductionmentioning
confidence: 99%