Reactor Design Pattern

In object-oriented (OO) applications, objects collaborate through message passing, which results in these objects being coupled and mutually dependent. These dependencies can be reactive, i.e. such that, for example, the state change of one object, requires automatic reaction in all dependent object...

Full description

Saved in:
Bibliographic Details
Published in:TEM Journal 2021-02, Vol.10 (1), p.18-30
Main Authors: Mijač, Marko, Garcia-Cabot, Antonio, Strahonja, Vjeran
Format: Article
Language:English
Subjects:
Automation
Collaboration
Energy and Environmental Studies
Informatics
Programming languages
Reactor design
Software upgrading
User interface
Citations: Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:In object-oriented (OO) applications, objects collaborate through message passing, which results in these objects being coupled and mutually dependent. These dependencies can be reactive, i.e. such that, for example, the state change of one object, requires automatic reaction in all dependent objects. Examples of such reactive dependencies can be found in various software systems, including rich graphical interfaces, spreadsheet systems, animation, robotics, etc. Unlike the reactive paradigm which natively provides abstractions and mechanisms for the management of reactive dependencies, the OO paradigm lacks proper support. Object-oriented applications developers often resort to the use of ad-hoc solutions or design patterns such as the well-known Observer pattern, which are not suitable for managing more complex scenarios. In this paper we offer a novel design pattern (REACTOR), which utilizes a graph data structure to improve the management of reactive dependencies in OO applications
ISSN:2217-8309
2217-8333
DOI:10.18421/TEM101-03