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
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
ZEO
Commits
6f585cc4
Commit
6f585cc4
authored
Jan 10, 2003
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Create a component for the ZEO schema, and make sure it gets installed.
parent
e23b02fd
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
58 additions
and
51 deletions
+58
-51
src/ZEO/component.xml
src/ZEO/component.xml
+55
-0
src/ZEO/schema.xml
src/ZEO/schema.xml
+3
-51
No files found.
src/ZEO/component.xml
0 → 100644
View file @
6f585cc4
<component>
<sectiontype
name=
"zeo"
>
<key
name=
"address"
datatype=
"socket-address"
required=
"yes"
>
<description>
The address at which the server should listen. This can be in
the form 'host:port' to signify a TCP/IP connection or a
pathname string to signify a Unix domain socket connection (at
least one '/' is required). A hostname may be a DNS name or a
dotted IP address. If the hostname is omitted, the platform's
default behavior is used when binding the listening socket (''
is passed to socket.bind() as the hostname portion of the
address).
</description>
</key>
<key
name=
"read-only"
datatype=
"boolean"
required=
"no"
default=
"false"
>
<description>
Flag indicating whether the server should operate in read-only
mode. Defaults to false. Note that even if the server is
operating in writable mode, individual storages may still be
read-only. But if the server is in read-only mode, no write
operations are allowed, even if the storages are writable. Note
that pack() is considered a read-only operation.
</description>
</key>
<key
name=
"invalidation-queue-size"
datatype=
"integer"
required=
"no"
default=
"100"
>
<description>
The storage server keeps a queue of the objects modified by the
last N transactions, where N == invalidation_queue_size. This
queue is used to speed client cache verification when a client
disconnects for a short period of time.
</description>
</key>
<key
name=
"transaction-timeout"
datatype=
"integer"
required=
"no"
>
<description>
The maximum amount of time to wait for a transaction to commit
after acquiring the storage lock, specified in seconds. If the
transaction takes too long, the client connection will be closed
and the transaction aborted.
</description>
</key>
</sectiontype>
</component>
src/ZEO/schema.xml
View file @
6f585cc4
...
@@ -8,59 +8,11 @@
...
@@ -8,59 +8,11 @@
</description>
</description>
<!-- Use the storage types defined by ZODB. -->
<!-- Use the storage types defined by ZODB. -->
<import
src=
"../ZODB/config.xml
"
/>
<import
package=
"ZODB
"
/>
<sectiontype
name=
"zeo"
>
<!-- Use the ZEO server information structure. -->
<import
package=
"ZEO"
/>
<key
name=
"address"
datatype=
"socket-address"
required=
"yes"
>
<description>
The address at which the server should listen. This can be in
the form 'host:port' to signify a TCP/IP connection or a
pathname string to signify a Unix domain socket connection (at
least one '/' is required). A hostname may be a DNS name or a
dotted IP address. If the hostname is omitted, the platform's
default behavior is used when binding the listening socket (''
is passed to socket.bind() as the hostname portion of the
address).
</description>
</key>
<key
name=
"read-only"
datatype=
"boolean"
required=
"no"
default=
"false"
>
<description>
Flag indicating whether the server should operate in read-only
mode. Defaults to false. Note that even if the server is
operating in writable mode, individual storages may still be
read-only. But if the server is in read-only mode, no write
operations are allowed, even if the storages are writable. Note
that pack() is considered a read-only operation.
</description>
</key>
<key
name=
"invalidation-queue-size"
datatype=
"integer"
required=
"no"
default=
"100"
>
<description>
The storage server keeps a queue of the objects modified by the
last N transactions, where N == invalidation_queue_size. This
queue is used to speed client cache verification when a client
disconnects for a short period of time.
</description>
</key>
<key
name=
"transaction-timeout"
datatype=
"integer"
required=
"no"
>
<description>
The maximum amount of time to wait for a transaction to commit
after acquiring the storage lock, specified in seconds. If the
transaction takes too long, the client connection will be closed
and the transaction aborted.
</description>
</key>
</sectiontype>
<section
type=
"zeo"
name=
"*"
required=
"yes"
attribute=
"zeo"
/>
<section
type=
"zeo"
name=
"*"
required=
"yes"
attribute=
"zeo"
/>
...
...
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