Open
Conversation
Author
|
This way my first contribution to open source project where I am trying to solved that basic issue 🙂 |
Contributor
|
Thank you @PratikKhaire ! The change itself looks really good. The only additional thing that needs to be done is that you need to sign your commit in order for the DCO check to pass. See instructions at https://github.com/hyperledger/fabric/pull/4310/checks?check_run_id=14876318045 |
yeasy
reviewed
Jul 8, 2025
| Starting with Fabric v2.4, client applications should use one of the Fabric Gateway client APIs (Go, Node, or Java), which are optimized to interact with the Fabric Gateway. These APIs expose the same high-level programming model which was initially introduced in Fabric v1.4. | ||
|
|
||
| Fabric Gateway (aka *the gateway*) manages the following transaction steps: | ||
| Fabric Gateway (aka _the gateway_) manages the following transaction steps: |
yeasy
reviewed
Jul 8, 2025
| The gateway will preferably select a peer in the same organization as the gateway peer and choose the peer | ||
| with the highest ledger block height. If no peer is available in the gateway's organization, then it will choose a peer | ||
| from another organization. | ||
| The gateway will preferably select a peer in the same organization as the gateway peer and choose the peer |
yeasy
reviewed
Jul 8, 2025
| The Gateway and its client APIs are designed to allow you, as a client application developer, to concentrate on the _business logic_ | ||
| of your application without having to concern yourself with the _infrastructure logic_ associated with a Fabric network. | ||
| As such, the APIs provide logical abstractions such as _organization_ and _contract_ rather than operational abstractions | ||
| such as _peer_ and _chaincode_. [Side note - clearly an admin API would want to expose these operational abstractions, |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Type of change
Description
By referring the issues no #3271
fixes the typo mistake in "Have"--->> "Having"
fix issue #3271
Additional details
Step to resolved issue
Go to website
clickhere
Screenshot :-
Here i am solved that issue #3271