Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZODB
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
Nicolas Wavrant
ZODB
Commits
04af5ea4
Commit
04af5ea4
authored
Jan 05, 2004
by
Tim Peters
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fixed a doc complaint.
parent
c755ce60
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
2 additions
and
2 deletions
+2
-2
doc/guide/prog-zodb.tex
doc/guide/prog-zodb.tex
+1
-1
doc/guide/zeo.tex
doc/guide/zeo.tex
+1
-1
No files found.
doc/guide/prog-zodb.tex
View file @
04af5ea4
...
...
@@ -99,7 +99,7 @@ implement the \class{Storage} interface.
\class
{
FileStorage
}
, which uses regular disk files, and
\class
{
bsddb3Storage
}
, which uses Sleepycat Software's BerkeleyDB
database. You could write a new Storage that stored objects in a
relational database
or Metakit file
, for example, if that would
relational database, for example, if that would
better suit your application. Two example storages,
\class
{
DemoStorage
}
and
\class
{
MappingStorage
}
, are available to use
as models if you want to write a new Storage.
...
...
doc/guide/zeo.tex
View file @
04af5ea4
...
...
@@ -30,7 +30,7 @@ XXX insert diagram here later
Any number of processes can create a
\class
{
ClientStorage
}
instance, and any number of threads in each process can be using that
instance.
\class
{
ClientStorage
}
aggressively caches objects
locally, so in order to avoid using stale data
. T
he ZEO server sends
locally, so in order to avoid using stale data
t
he ZEO server sends
an invalidation message to all the connected
\class
{
ClientStorage
}
instances on every write operation. The invalidation message contains
the object ID for each object that's been modified, letting the
...
...
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