The addition of event-driven programming capacities to the Logtalk language [Moura94] is based on a simple but powerful idea:
The computations must result, not only from message sending, but also from the observation of message sending.
The need to associate computations to the occurrence of events was very early recognized in knowledge representation languages, programming languages [Stefik_et_al_86], [Moon86], operative systems [Tanenbaum87], and graphical user interfaces.
With the integration between object-oriented and event-driven programming, we intend to achieve the following goals:
- Minimize the coupling between objects. An object should only contain what is intrinsic to it. If an object observes another object, that means that it should depend only on the public protocol of the object observed and not on the implementation of that protocol.
- Provide a mechanism for building reflexive systems in Logtalk based on the dynamic behavior of objects in complement to the reflective information on object predicates and relations.
- Provide a mechanism for easily defining method pre- and post-conditions that can be toggled using the events compiler flag. The pre- and post-conditions may be defined in the same object containing the methods or distributed between several objects acting as method monitors.
- Provide a publish-subscribe mechanism where public messages play the role of events.
The words event and monitor have multiple meanings in computer science. To avoid misunderstandings, we start by defining them in the Logtalk context.
In an object-oriented system, all computations start through message
sending. It thus becomes quite natural to declare that the only event
that can occur in this kind of system is precisely the sending of a
message. An event can thus be represented by the ordered tuple
(Object, Message, Sender).
If we consider message processing an indivisible activity, we can
interpret the sending of a message and the return of the control to the
object that has sent the message as two distinct events. This
distinction allows us to have a more precise control over a system
dynamic behavior. In Logtalk, these two types of events have been named
after, respectively for sending a message and for
returning of control to the sender. Therefore, we refine our event
representation using the ordered tuple
(Event, Object, Message, Sender).
The implementation of events in Logtalk enjoys the following properties:
- Independence between the two types of events
- We can choose to watch only one event type or to process each one of the events associated to a message sending in an independent way.
- All events are automatically generated by the message sending mechanism
- The task of generating events is transparently accomplished by the message sending mechanism. The user only needs to define the events that will be monitored.
- The events watched at any moment can be dynamically changed during program execution
- The notion of event allows the user not only to have the possibility of observing, but also of controlling and modifying an application behavior, namely by dynamically changing the observed events during program execution. It is our goal to provide the user with the possibility of modeling the largest number of situations.
Complementary to the notion of event is the notion of monitor. A monitor is an object that is automatically notified by the message sending mechanism whenever a registered event occurs. Any object that defines the event-handling predicates can play the role of a monitor.
The implementation of monitors in Logtalk enjoys the following properties:
- Any object can act as a monitor
- The monitor status is a role that any object can perform during its existence. The minimum protocol necessary is declared in the built-in monitoring protocol. Strictly speaking, the reference to this protocol is only needed when specializing event handlers. Nevertheless, it is considered good programming practice to always refer the protocol when defining event handlers.
- Unlimited number of monitors for each event
- Several monitors can observe the same event because of distinct reasons. Therefore, the number of monitors per event is bounded only by the available computing resources.
- The monitor status of an object can be dynamically changed in runtime
- This property does not imply that an object must be dynamic to act as a monitor (the monitor status of an object is not stored in the object).
- Event handlers cannot modify the event arguments
- Notably, if the message contains unbound variables, these cannot be bound by the calls to the monitor event handlers.
Assuming that the events flag is set to
the object (or category) sending the messages we want to observe, for each
message that is sent using the (::)/2 control
construct, the runtime system automatically generates two events.
The first — before event — is generated when the message is sent. The
second — after event — is generated after the message has successfully
Note that self messages (using the (::)/1 control construct) or super calls (using the (^^)/1 control construct) don’t generate events.
Communicating events to monitors¶
Whenever a spied event occurs, the message sending mechanism calls the corresponding event handlers directly for all registered monitors. These calls are internally made bypassing the message sending primitives in order to avoid potential endless loops. The event handlers consist in user definitions for the public predicates declared in the built-in monitoring protocol (see below for more details).
Ideally, the existence of monitored messages should not affect the processing of the remaining messages. On the other hand, for each message that has been sent, the system must verify if its respective event is monitored. Whenever possible, this verification should be performed in constant time and independently of the number of monitored events. The events representation takes advantage of the first argument indexing performed by most Prolog compilers, which ensure — in the general case — access in constant time.
Event-support can be turned off on a per-object (or per-category) basis using the events compiler flag. With event-support turned off, Logtalk uses optimized code for processing message sending calls that skips the checking of monitored events, resulting in a small but measurable performance improvement.
The established semantics for monitors actions consists on considering its success as a necessary condition so that a message can succeed:
- All actions associated to events of type
beforemust succeed, so that the message processing can start.
- All actions associated to events of type
afteralso have to succeed so that the message itself succeeds. The failure of any action associated to an event of type
afterforces backtracking over the message execution (the failure of a monitor never causes backtracking over the preceding monitor actions).
Note that this is the most general choice. If we wish a transparent presence of monitors in a message processing, we just have to define the monitor actions in such a way that they never fail (which is very simple to accomplish).
Activation order of monitors¶
Ideally, whenever there are several monitors defined for the same event,
the calling order should not interfere with the result. However, this is
not always possible. In the case of an event of type
failure of a monitor prevents a message from being sent and prevents the
execution of the remaining monitors. In case of an event of type
after, a monitor failure will force backtracking over message
execution. Different orders of monitor activation can therefore lead to
different results if the monitor actions imply object modifications
unrecoverable in case of backtracking. Therefore, the order for monitor
activation should be assumed as arbitrary. In effect, to assume or to
try to impose a specific sequence requires a global knowledge of an
application dynamics, which is not always possible. Furthermore, that
knowledge can reveal itself as incorrect if there is any changing in the
execution conditions. Note that, given the independence between
monitors, it does not make sense that a failure forces backtracking over
the actions previously executed.
Logtalk provides three built-in predicates for event handling. These predicates support defining, enumerating, and abolishing events. Applications that use events extensively usually define a set of objects that use these built-in predicates to implement more sophisticated and higher-level behavior.
Defining new events¶
New events can be defined using the define_events/5 built-in predicate:
| ?- define_events(Event, Object, Message, Sender, Monitor).
Note that if any of the
Sender arguments is a free variable or contains free variables, this
call will define a set of matching events.
Abolishing defined events¶
Events that are no longer needed may be abolished using the abolish_events/5 built-in predicate:
| ?- abolish_events(Event, Object, Message, Sender, Monitor).
If called with free variables, this goal will remove all matching events.
Finding defined events¶
The events that are currently defined can be retrieved using the current_event/5 built-in predicate:
| ?- current_event(Event, Object, Message, Sender, Monitor).
Note that this predicate will return sets of matching events if some of the returned arguments are free variables or contain free variables.
Defining event handlers¶
The monitoring built-in protocol declares two
public predicates, before/3 and after/3, that
are automatically called to handle
after events. Any
object that plays the role of monitor must define one or both of these
event handler methods:
before(Object, Message, Sender) :- ... . after(Object, Message, Sender) :- ... .
The arguments in both methods are instantiated by the message sending
mechanism when a monitored event occurs. For example, assume that we
want to define a monitor called
tracer that will track any message
sent to an object by printing a describing text to the standard output.
Its definition could be something like:
:- object(tracer, % built-in protocol for event handler methods implements(monitoring)). before(Object, Message, Sender) :- write('call: '), writeq(Object), write(' <-- '), writeq(Message), write(' from '), writeq(Sender), nl. after(Object, Message, Sender) :- write('exit: '), writeq(Object), write(' <-- '), writeq(Message), write(' from '), writeq(Sender), nl. :- end_object.
Assume that we also have the following object:
:- object(any). :- public(bar/1). bar(bar). :- public(foo/1). foo(foo). :- end_object.
After compiling and loading both objects and setting the
events flag to
allow, we can start tracing
every message sent to any object by calling the
define_events/5 built-in predicate:
| ?- set_logtalk_flag(events, allow). yes | ?- define_events(_, _, _, _, tracer). yes
From now on, every message sent from
user to any object will be
traced to the standard output stream:
| ?- any::bar(X). call: any <-- bar(X) from user exit: any <-- bar(bar) from user X = bar yes
To stop tracing, we can use the abolish_events/5 built-in predicate:
| ?- abolish_events(_, _, _, _, tracer). yes
The monitoring protocol declares the event handlers as public predicates. If necessary, protected or private implementation of the protocol may be used in order to change the scope of the event handler predicates. Note that the message sending processing mechanism is able to call the event handlers irrespective of their scope. Nevertheless, the scope of the event handlers may be restricted in order to prevent other objects from calling them.
The pseudo-object user can also act as a monitor.
This object expects the
after/3 predicates to be
defined in the plain Prolog database. To avoid predicate existence errors
user as a monitor, this object declares the predicates
multifile. Thus, any plain Prolog code defining the predicates should
include the directives:
:- multifile(before/3). :- multifile(after/3).