Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add response hooks #50

Merged
merged 3 commits into from
Dec 3, 2019
Merged

Add response hooks #50

merged 3 commits into from
Dec 3, 2019

Conversation

hannahhoward
Copy link
Collaborator

Goals

Add ability to process incoming responses and halt requests as neccesary

Implementation

  • define interface for adding response hooks
  • process response hooks when responses are received
  • refactor integration tests to simplify them

@hannahhoward hannahhoward force-pushed the feat/response-hooks branch 2 times, most recently from 7c979e2 to ebbe656 Compare November 19, 2019 22:29
Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

hannahhoward and others added 3 commits December 2, 2019 16:33
define types and mock implementation for supporting extensions
Add processing of on extensions in responses in the request manager
DRY up integration test so it's more clear what each test is doing
@hannahhoward hannahhoward changed the base branch from feat/request-hooks to master December 3, 2019 00:33
@hannahhoward hannahhoward merged commit 93f5724 into master Dec 3, 2019
@mvdan mvdan deleted the feat/response-hooks branch December 15, 2021 14:15
marten-seemann pushed a commit that referenced this pull request Mar 2, 2023
* feat(encoding): add library to handle encoding

Create a new library for general type encoding

* feat(registry): add simple registry

add a simple threadsafe registry to handle registering types like vouchers

* feat(datatransfer): incorporate registry

incorporate registry into data transfer module

* feat(message): move decoding inside messages

Move encode/decode inside the message -- so that we can insure cbor encodable values, and then use
cbg.Deferred later

* feat(message): convert to cbg.Deferred

convert messages to use cbg.Deferred so that the whole message is a proper CBOR value and also move
selector encoding inside the message

* refactor(graphsync): remove utils

remove utils.go which is not used

* refactor(registry): move types to root

move Identifier & Registerable to root types package

* refactor(datatransfer): minor refactors and cleanups
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants