forked from a2aproject/a2a-java
-
Notifications
You must be signed in to change notification settings - Fork 0
Client transport config #1
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
Open
brasseld
wants to merge
31
commits into
fjuma:client_agnostic_transport
Choose a base branch
from
brasseld:client_transport_config
base: client_agnostic_transport
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Client transport config #1
brasseld
wants to merge
31
commits into
fjuma:client_agnostic_transport
from
brasseld:client_transport_config
Conversation
This file contains hidden or 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
… and also split out the http client code into a separate module
…text, ClientConfig, and ClientCallInterceptor similar to the Python SDK. Introduce a ClientTransportProvider and update the JSONRPC and gRPC transport implementations. Introduce a new Client and ClientFactory implementations.
… to make use of it, and remove the http-client and grpc dependencies from the client config module
…t to be able to make use of the appropriate client based on the transport and update the JSONRPC and gRPC tests to extend this
…otificationConfig
…roto#pushNotificationConfig
…gets cached once retrieved
…d some convenience methods to AbstractClient
…t other server implementations that also support JSONRPC can make use of these tests. These tests will be skipped when testing other transports
…text, ClientConfig, and ClientCallInterceptor similar to the Python SDK. Introduce a ClientTransportProvider and update the JSONRPC and gRPC transport implementations. Introduce a new Client and ClientFactory implementations.
3 tasks
c826f3a to
26ab76d
Compare
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 PR is a proposal to make the transport configuration specific to a given transport implementation.
This one will ease developer experience by providing a builder for configuring a Client in a more stricter way compare to what exists today.
Also, this will help at getting rid of strong coupling with different transport implementations.
Two benefits: