Model-based, event-driven programming paradigm for interactive web applications

Abstract

Model-based, event-driven programming paradigm for interactive web applications The MIT Faculty has made this article openly available. Please share how this access benefits you. Your story matters. Citation Aleksandar Milicevic, Daniel Jackson, Milos Gligoric, and Darko Marinov. 2013. Model-based, event-driven programming paradigm for interactive web applications. In Proceedings of the 2013 ACM international symposium on New ideas, new paradigms, and reflections on programming & software (Onward! '13). ACM,

Derailer

“…The uniformity of security policies suggests that it would be profitable to pursue designs with a stronger separation of concerns, with policy more cleanly separated from functionality (and indeed this is the direction seen in many new developments, both in our own group [16] and elsewhere [24,27], that allow policies to be expressed declaratively, in one place, and enforced globally). Such a move would of course make our analysis less useful, but this seems to us the inevitable push-pull between synthesis and analysis.…”

Precise, dynamic information flow for database-backed applications

“…Our approach addresses information flow as opposed to access control [23,31,34], which prevents leaks at application endpoints and does not address indirect or implicit flows. Similarly, work on multi-level databases [21,30] focuses on the storage and access control issues surrounding data at different levels of access in the database.…”

Blending Event-Based and Multi-Agent Systems Around Coordination Abstractions

“…In the overall, EBS are basically coordinated systems, where coordination is event-based [18]: process activities are mostly driven by event notifications generated by producers; transformed, aggregated, filtered, distributed by the event bus; and finally interpreted and used by consumers. Producer / consumer coordination is then mediated by the event bus, working as the system coordinator, which encapsulates and possibly automates most of the coordination activities in an EBS.…”

“…From the MAS viewpoint, this means that the role of coordination models in MAS [6] is to provide event-driven coordination media governing event coordination in MAS. From the EBS viewpoint, coordination in EBS is event-based [18], and the event bus and service work as the system coordinators. This means that coordination media could work as the core for an event-based architecture, and that EBS could be grounded in principle upon a suitably-expressive coordination middleware, designing the event bus around the coordination services [30].…”