2. Object Oriented Paradigm
for Distributed Programming
AS
Functional classes:
Sequential in terms of methods
Contain attributes and methods
3. Synchronization Classes:
Encapsulates objects and locations
Routing of methods
Configuration Classes
Encapsulate the methods applied to
synchronize the methods of the objects
CONT….
4. What is Object?
• Status of the object action , define the division of
the object into fragments
• Defines the methods of the objects
• Division of classes by their functionalities
• Same as the sequential
object oriented
,
Functional Classes:
5. First time Use
• The above ideas were first implemented [and a model called “hierarchical
software components for reusability
“ (abbreviated hector)”
6. SYNCHRONIZATION CLASSES
When object will be used?
Implicit synchronizer
Use Multiple inheritance mechanism
Managed by designer level
Synchronize execution of methods
Provide coordination between the
sequential language
7. New kind of software components reusable
with various function classes encapsulates
configuration schemes
Encapsulates circulating tokens can be readily
reuse
To represent topology and each topology will
process a state
Representative of finite
set of evolution rules
2019
What is Configuration Classes?
8. Roles of Configuration Classes
Represent connective object
migration primitive
Deletion primitive
Creation primitive
replacement of object
Addition of new site
Addition and verification of methods
Manage and balance load
9. Roles of Configuration Classes
Represent connective object
migration primitive
Deletion primitive
Creation primitive
replacement of object
Addition of new site
Addition and verification of methods
Manage and balance load
10. Example
For example, the presence of representative R on site
H will be denoted by H ( R ), and the absence of representative R
on site.
H will be denoted by -H ( R ).
the (( not H and (( and )) logical connectors will be respectively
denoted ‘-I and ‘,’.
12. Due to the use of object oriented paradigms, some
components can readily be reused to solve different
problems. In addition, sites can be used more
efficiently.
For example, it will be easy to change the
configuration class according to the topology or
the power of the sites.
Using the inheritance mechanism renders
distribution policies transparent to the application
(or class) users
2019
CRUX