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
3949f683
Commit
3949f683
authored
Sep 01, 2009
by
Benji York
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
fix typos
parent
704673e9
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
src/ZEO/protocol.txt
src/ZEO/protocol.txt
+5
-5
No files found.
src/ZEO/protocol.txt
View file @
3949f683
...
...
@@ -4,7 +4,7 @@ ZEO Network Protocol (sans authentication)
This document describes the ZEO network protocol. It assumes that the
optional authentication protocol isn't used. At the lowest
level, the protocol consists of sized messages. All communication
btween the client and server consists of sized messages. A sized
b
e
tween the client and server consists of sized messages. A sized
message consists of a 4-byte unsigned big-endian content length,
followed by the content. There are two subprotocols, for protocol
negotiation, and for normal operation. The normal operation protocol
...
...
@@ -19,7 +19,7 @@ strings, the client and server switch to RPC mode.
The RPC protocol uses messages that are pickled tuples consisting of:
message_id
The message id is used to match repl
y
s with requests, allowing
The message id is used to match repl
ie
s with requests, allowing
multiple outstanding synchronous requests.
async_flag
...
...
@@ -39,15 +39,15 @@ args
After making a connection and negotiating the protocol, the following
interactions occur:
- The client requests the athentication protocol by calling
- The client requests the a
u
thentication protocol by calling
getAuthProtocol. For this discussion, we'll assume the server
returns None. Note that if the server doesn't require
authentication, this step is optional.
- The client calls register passing a storage identifier and a
read-only flag. The server doesn't return a value, but it may raise
an exception either if the storage doesn't exist, or if the
the
st
ro
age is readonly and the read-only flag passed by the client is
an exception either if the storage doesn't exist, or if the
st
or
age is readonly and the read-only flag passed by the client is
false.
At this point, the client and server send each other messages as
...
...
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