SVN: ZODB/trunk/3.11.txt *** empty log message ***

Jim Fulton <[email protected]> Thu, 1 Mar 2012 07:03:24 -0500 (EST)
Newsgroups gmane.comp.python.zope.zodb.cvs
Message-ID <20120301120324.15A2394202__21018.6746590354$1330603410$gmane$org@cvs.zope.org>
Log message for revision 124495:
  *** empty log message ***

Changed:
  U   ZODB/trunk/3.11.txt

-=-
Modified: ZODB/trunk/3.11.txt
===================================================================
--- ZODB/trunk/3.11.txt	2012-03-01 09:02:31 UTC (rev 124494)
+++ ZODB/trunk/3.11.txt	2012-03-01 12:03:23 UTC (rev 124495)
@@ -27,3 +27,18 @@
 
 - persistent.Object, which handles the common case of a simple object
   that just has some data. (The moral equivalent of a JS object. :)
+
+- API to preload objects.
+
+  Say you know you're going to oterate over an array of objects, you
+  might signal that intend to use the object with something like::
+
+    for oject in objects:
+        object._p_will_use()
+
+  (I think there's an RFC for something like this.)
+
+  For most storages, _p_will_use won't have any effect, but for ZEO,
+  it could cause a load request to be sent to the server if the object
+  isn't already loaded or in the zeo cache. This way, you could have
+  lots of loads in flight at once, mitigating round-trip costs.