Differences

This shows you the differences between two versions of the page.

--- weca [2011/06/27 05:05]
aspectscript
+++ weca [2012/02/29 13:50] (current)
aspectscript
@@ Line 1: / Line 1: @@
 ====== WeCa: Modular and Flexible Causality Control on the Web ======
+** NOTE: There is an update of this Web page [[http://pleiad.cl/otm/wiki/weca|here]], please visit it. This Web page will be removed soon.**
 [[http://en.wikipedia.org/wiki/Ajax_%28programming%29|Ajax]] has allowed JavaScript programmers to create interactive, collaborative, and user-centered Web applications, known
-as Web 2.0 Applications. These Web applications behave as distributed systems because processors are user machines that are used to send and receive messages between one another. Unsurprisingly, these applications have to address the same causality issues present in distributed systems like the need a) to control the causality between messages sent and responses received and b) to react to distributed causal relations. JavaScript programmers overcome these issues using rudimentary and alternative techniques that largely ignore the distributed computing theory. In addition, these techniques are not very flexible and need to intrusively modify these Web applications. In this paper, we study how causality issues affect these applications and present WeCa, a practical library that allows for modular and flexible control over these causality issues in Web applications. In contrast to current proposals, WeCa is based on [[http://en.wikipedia.org/wiki/Aspect-oriented_programming|aspects]] and [[http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.102.7917|stateful aspects]], [[http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=603392|message ordering strategies]], and  [[http://en.wikipedia.org/wiki/Vector_clock|vector clocks]]. We illustrate WeCa in action with several practical examples from the realm of Web applications. For instance, we analyze the flow of information in Web applications like Twitter using WeCa.
+as Web 2.0 Applications. These Web applications behave as distributed systems because processors are user machines that are used to send and receive messages between one another. Unsurprisingly, these applications have to address the same causality issues present in distributed systems like the need a) to control the causality between messages sent and responses received and b) to react to distributed causal relations. JavaScript programmers overcome these issues using rudimentary and alternative techniques that largely ignore the distributed computing theory. In addition, these techniques are not very flexible and need to intrusively modify these Web applications. We study how causality issues affect these applications and present WeCa, a practical library that allows for modular and flexible control over these causality issues in Web applications. In contrast to current proposals, WeCa is based on [[http://en.wikipedia.org/wiki/Aspect-oriented_programming|aspects]] and [[http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.102.7917|stateful aspects]], [[http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=603392|message ordering strategies]], and  [[http://en.wikipedia.org/wiki/Vector_clock|vector clocks]]. We illustrate WeCa in action with several practical examples from the realm of Web applications. For instance, we analyze the flow of information in Web applications like Twitter using WeCa.
 {{ :wov2.png?432x301 |}}
+The figure shows the needs of causality of Web applications and how WeCa proposes to satisfy these needs. In this Web site, you can find examples of these needs:
-Here, you can find examples where WeCa is used:
   * [[otm/ordering_of_messages| Controlling Message Causality]]