Author: jmorliaguet
Date: Wed Feb 15 13:03:24 2006
New Revision: 2387
Modified:
cpsskins/branches/jmo-perspectives/ui/framework/tests/zope3/functional/latency/cpsskins_latency.pt
Log:
- fixed typos
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:03:24 2006
@@ -93,18 +93,18 @@
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.
+ user performs many actions in a short time period, the results of these
+ actions will be presented 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).
+ the other requests (useful when typing text, when cancelling, etc.).
</dd>
<dt>QUEUE SEQUENCE (FIFO)</dt>
- <dd>The first request is fulfilled before the other requests .</dd>
+ <dd>The request order is respected.</dd>
</dl>
<p>In the example below, some data (1 .. 10) is written in a remote storage
@@ -112,9 +112,7 @@
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>
-
-
+ being stored in the specified order.</p>
<!-- models -->
<ins class="model">
--
http://lists.nuxeo.com/mailman/listinfo/z3lab-checkins
