Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZEO
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
ZEO
Commits
437b67d2
Commit
437b67d2
authored
Mar 01, 2012
by
Jim Fulton
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
*** empty log message ***
parent
aca216b3
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
0 deletions
+15
-0
3.11.txt
3.11.txt
+15
-0
No files found.
3.11.txt
View file @
437b67d2
...
...
@@ -27,3 +27,18 @@ These aren't promises, but things I'd like to do:
- 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.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment