Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
C
capnproto
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
capnproto
Commits
0c2fa6b7
Commit
0c2fa6b7
authored
Nov 12, 2013
by
Kenton Varda
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Tweak a comment.
parent
5fe62e13
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
5 deletions
+6
-5
rpc.capnp
c++/src/capnp/rpc.capnp
+6
-5
No files found.
c++/src/capnp/rpc.capnp
View file @
0c2fa6b7
...
...
@@ -455,11 +455,12 @@ struct Restore {
#
# Level 0/1 implementations need to implement a limited version of `Restore` only for the purpose
# of bootstrapping a new connection (otherwise, there would be no objects to which to address
# methods). These levels may simply implement singleton services that exist for the lifetime of
# the host process and probably have non-secret names. A level 0 receiver of `Restore` should
# never actually send a `Return` message, but should simply expect `Call` messages addressed to
# the `PromisedAnswer` corresponding to the `Restore`. A level 0 sender of `Restore` can ignore
# the corresponding `Return` and just keep addressing the `PromisedAnswer`.
# methods). These levels may simply implement public singleton services that exist for the
# lifetime of the host process and probably have non-secret names. A level 0 receiver of
# `Restore` should never actually send a `Return` message, but should simply expect `Call`
# messages addressed to the `PromisedAnswer` corresponding to the `Restore`. A level 0 sender
# of `Restore` can ignore the corresponding `Return` and just keep addressing the
# `PromisedAnswer`.
questionId @0 :QuestionId;
# A new question ID identifying this request, which will eventually receive a Return message
...
...
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