Steven Allen
Steven Allen
My concerns with sqlite are: * Cgo build * dynamic libraries * binary size (if we go with static bindings) * the goC latency. Ideally we'd have some kind of...
cc @raulk?
Yup, agreed. Although it _would_ be nice to actually implement `CannotConnect`.
> Not feasible because TTL management needs to be fine-grained (up to the multiaddr). We can also manage this using a GC system. That is, store large records and periodically...
We need to go the other way and actually build a resource manager that can be used by applications (ideally one that _doesn't_ live in libp2p, but that is shared...
Update: We've punted this for now in favor of using a single event that optionally includes the signed record. We still want to be able to react to available events,...
My usecase is implementing a parallel multirouter (i.e., a router that queries multiple sub-routers in parallel).
Ideally, we'd just not store addresses in peer records twice. That is, we'd: 1. Assign a TTL to the entire peer record. 2. When returning the addresses for a peer,...
This sounds like a reasonable addition.
What's your use-case? At the moment, this isn't a really high priority for go-libp2p itself.