Remove op:bootstrap and instead always export at 0
#84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This removes the `op:bootstrap` operation which used to ask the remote node make available the bootstrap object and would setup a promise. That is almost always unnessesery as the bootstrap object is needed to do anything useful with CapTP and so must always be issued. This instead removes the operation and just makes it required that after a successful `op:start-session` exchange the bootstrap object be exported at position `0` which simplifies the spec.
Closed
|
@tsyesika I hadn't realized this was a PR so isn't subject to "record consensus by closing"... I'll put this on the agenda for November |
Closed
|
We have decided last meeting (November 2023) to merge this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes the
op:bootstrapoperation which used to ask the remote node make available the bootstrap object and would setup a promise. That is almost always unnecessary as the bootstrap object is needed to do anything useful with CapTP and so must always be issued.This instead removes the operation and just makes it required that after a successful
op:start-sessionexchange the bootstrap object be exported at position0which simplifies the spec.