G. Starovic, V. Cahill, and B. Tangney. The ECO model: Events + constraints + objects. Technical report, Dept. of Computer Science, Trinity College Dublin, Ireland, February 1995. Technical report TCD-CS-95-05.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....communication across a distributed system. In order to scale well, SECO features notify constraints that are dynamically linkable. 5.1 ECO Event Model Architecture The abbreviation ECO stands for Events, Constraints and Objects, which are the three central concepts used in the ECO event model. [SCT95a] and [SCT95b] describe the rationale of the ECO event model, the three central concepts and ECO s event application interface. In the following Sections, we first explain ECO s three central concepts, then introduce ECO s event applications interface with its three operations, and finally we ....

G. Starovic, V. Cahill, and B. Tangney. The ECO model: Events + constraints + objects. Technical report, Dept. of Computer Science, Trinity College Dublin, Ireland, February 1995. Technical report TCD-CS-95-05.

....only some events need to be ordered with respect to one another in order to maintain the directory s integrity. However, our programmed solutions to the agreement problem are ad hoc, and we are working on a programming framework for application writers, to support them in expressing constraints [22] as well as dependencies. ....

G. Starovic, V. Cahill and B. Tangney (1995), The ECO model: events+constraints+objects. Tech report, dept. of Computer Science, Trinity College Dublin.

....design, it provides a useful abstraction, as it removes many of the complexities of dealing with pointers to methods. The issues related to the depth of a transition are dealt with later. 2.6.4. 2 C ECO Code While the syntax for the Entity class attempts to remain faithful to that proposed in [56], the purpose of this example is to demonstrate the overall mechanism, rather than the specific syntax. class Example int x; Attributes Inc ( x Actions depList pDepList; Depart on lists depList qDepList; inevents pEevent, qEvent; Declare events. Preconditions constraint ....

Gradimir Starovic & Vinny Cahill & Andrew Condon & Stephen McGerty & Karl O'Connell & Gradimir Starovic & Brendan Tangney. The eco model: Events + constraints + objects. Technical report, Distributed Systems Group, Trinity College Dublin, 95.

....objects. It maintains information about classes, objects, events and their occurrences, and information about various bindings. It knows about a number of predefined events. The library itself uses events. More about the ECO model, and a programming language syntax for this model, can be found in [53], reproduced in appendix C. The separation of functionality between the ECOlib and its client is shown in figure 3.1. ECOlib ECOlib client announces events: user defined pre defined (un)subscribes from to events processes events using: enqueue, dequeue, process active, process passive, ....

....invoke the application level code which implements the method. Different programming language constructs (from the same language or from different languages) may be translated into the code which will use the ECOlib interface. There is an obvious mapping from the language constructs described in [53] and the primitives and predefined events described in this chapter. 3.2 The ECOlib interface This section specifies the ECOlib entry points or primitives, and a collection of the predefined events. 3.2.1 The ECOLib internals This subsection describes some internal ECOlib data (the event ....

G. Starovic, V. Cahill, and B. Tangney. The ECO model: events + constraints + objects, February 1995. Submitted to the Usenix Conference on Object-Oriented Technologies 95.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC