Petar Maymounkov

Hi Gerard. Yes, the purpose is performance. With a persistent local cache the client only fetches what has changed since last time the user used the app. This issue has...

Here's some slides, mostly saying the same thing: https://docs.google.com/presentation/d/1CN4hh2TtmK8YZN0i3iCtbor3fnnixdz9Cw0wASh6HVw/edit?usp=sharing

PROBLEM: A fixed concurrency parameter alpha is not appropriate for both early stage and late stage queries. PROPOSAL: We do away with the current use of ALPHA, which is to...

@Stebalien @aarshkshah1992 @aschmahmann can you review the proposal above and chime in?

Sounds good. We can keep the cap. This PR requires some change in the DHT parameters and respective configs. Parameters used to be alpha and beta. With this change they...

Sounds good.

Note that I have a complete implementation of this feature: https://github.com/libp2p/go-libp2p-kad-dht/tree/petar/accel You could start from that?

@aschmahmann This division into two categories makes perfect sense. These two layers are bitswap/graphsync-specific in my mind. To complete the picture, I would introduce a third layer which lives outside...

@dworthen I agree we should transition to a uniform result structure. I've done this in https://github.com/gov4git/gov4git/pull/167 In your example, `response` and `status` seem to have an overlapping function. They both...

@dworthen https://github.com/gov4git/gov4git/pull/167 resolves the issue with returning a structured result. See the updated PR description for the details https://github.com/gov4git/gov4git/pull/167 Next is your request to return more informative error messages and...