Author: jmorliaguet
Date: Wed Feb 15 13:00:14 2006
New Revision: 2386
Modified:
cpsskins/branches/jmo-perspectives/ui/framework/tests/zope3/functional/latency/cpsskins_latency.pt
Log:
- doc update
Modified:
cpsskins/branches/jmo-perspectives/ui/framework/tests/zope3/functional/latency/cpsskins_latency.pt
==============================================================================
---
cpsskins/branches/jmo-perspectives/ui/framework/tests/zope3/functional/latency/cpsskins_latency.pt
(original)
+++
cpsskins/branches/jmo-perspectives/ui/framework/tests/zope3/functional/latency/cpsskins_latency.pt
Wed Feb 15 13:00:14 2006
@@ -9,8 +9,6 @@
type="text/javascript"></script>
<script src="/++skin++cpsskins/@@/++resource++json.js"
type="text/javascript"></script>
- <script src="/++skin++cpsskins/@@/++resource++ctal.js"
- type="text/javascript"></script>
<script src="/++skin++cpsskins/@@/++resource++cpsskins.js"
type="text/javascript"></script>
<link rel="stylesheet" type="text/css"
@@ -88,7 +86,35 @@
</head>
<body>
- <h1>CPSSkins: network latency</h1>
+ <h1>CPSSkins: controlling network latency</h1>
+
+ <p>Because they do asynchronous calls, AJAX applications often receive the
+ results of a series of requests in an order completely different from
+ the order in which the requests were originally made.</p>
+
+ <p>If the network or the server response latency is significant, or if the
+ user performs many actions in a short time, the results of these actions
+ user will be performed in an unpredictable sequence.
+ A solution is to specify access rules for the data storage:<p>
+
+ <dl>
+ <dt>STACK SEQUENCE (LIFO)</dt>
+ <dd>The last request gets highest priority, it will be fulfilled before
+ the other requests (useful when typing).
+ </dd>
+
+ <dt>QUEUE SEQUENCE (FIFO)</dt>
+ <dd>The first request is fulfilled before the other requests .</dd>
+ </dl>
+
+ <p>In the example below, some data (1 .. 10) is written in a remote storage
+ in the following order: 1, 2, 3, ... 10. The results are displayed as soon
+ as the client gets a response from the server.</p>
+
+ <p>The storages that specify an access sequence are guaranteed to see the
data
+ being stored in the specifed order.</p>
+
+
<!-- models -->
<ins class="model">
--
http://lists.nuxeo.com/mailman/listinfo/z3lab-checkins
