JSON format expected from general peer [GEN -> DEP] #52
centauri1219
started this conversation in
Ideas
Replies: 2 comments 2 replies
-
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
we also need a target peerID key in the request. the target peerID is required in the routing logic. the target peerID refers to the peer with which you want to communicate eventually. For eg-: if I want to communicate with a D1 peer, i need the peerID of that peer in the query as well. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The depth peer will require the following JSON format from the general peer at each depth iteration in the case of querying.
In the case of indexing we also need file metadata.
@YugDalwadi @SiddhantGahankari @Abhinav-Kumar2 @IshatV412 Check out the fields and do suggest changes on additional or different return types that may be required.
Beta Was this translation helpful? Give feedback.
All reactions