amazon

Saturday, August 22, 2015

A SUITABLE PROGRAMMING MODEL FOR ERROR CONTROL IN NETWORK ENVIRONMENT.

A suitable programming model for error           Control in network environment.

Abstract:

  The capability of dynamically adapting to distinct runtime conditions is an important issue when designing distributed systems where negotiated quality of service (QoS) cannot always be delivered between processes.
  Providing error control for such dynamic environments is a challenging task. Considering such a context, this paper proposes an adaptive programming odel for fault-tolerant distributed computing, which provides upper-layer applications with process state information according to the current system synchrony (or QoS).
  The underlying system model is hybrid, composed by a synchronous part (where there are time bounds on processing speed and message delay) and an asynchronous part (where there is no time bound). Moreover, processes are not required to share the same view of the system synchrony at a given time.
  To illustrate what can be done in this programming model and how to use it, the consensus problem is taken as a benchmark problem. This paper also presents an implementation of the model that relies on a negotiated quality of service (QoS) for communication channels.





Existing System:
Ø The existing system is usually called a time-free asynchronous distributed system prone to process crashes.
Ø In these systems, a system designer can only assume an upper bound on the number of processes that can crash and, consequently, design protocols relying on the assumption that at least processes are alive.
Ø The protocol has no means to know whether a given process is alive or not.
 Proposed System:

Ø Our model provides upper-layer applications with process state information according to the current system synchrony (or QoS).
Ø The underlying system model is hybrid, comprised of a synchronous part and an asynchronous part. However, such a composition can vary over time in such a way that the system may become totally synchronous or totally asynchronous

         












System Requirements
Hardware:
PROCESSOR                    :    PENTIUM IV 2.6 GHz
RAM                        :     512 MB
MONITOR               :     15”
HARD DISK            :     20 GB
CDDRIVE                :     52X
KEYBOARD           :     STANDARD 102 KEYS
MOUSE                    :     3 BUTTONS


Software:
FRONT END                    :    JAVA, SWING
TOOLS USED                  :    JFRAME BUILDER
OPERATING SYSTEM   :    WINDOWS XP



No comments:

Post a Comment