- 20 Apr, 2021 1 commit
-
-
Cory Schwartz authored
-
- 01 Apr, 2021 3 commits
- 30 Mar, 2021 1 commit
-
-
vyzo authored
-
- 29 Mar, 2021 2 commits
-
-
Steven Allen authored
Given 1k requests per second (assuming one stream per request), we can easily loop around the stream ID after less than 2 months. 32bits is plenty (usually) for connection-scoped stream IDs because individual connections don't usually last that long, but isn't enough for a _global_ stream ID. Given that there's no reason for these to be 32bit IDs, let's just make them 64bits.
-
Steven Allen authored
This way, transports with shared resources (e.g., reused sockets) can clean them up. fixes https://github.com/libp2p/go-libp2p/issues/999
-
- 19 Mar, 2021 2 commits
-
-
Steven Allen authored
-
Steven Allen authored
Given two relay connections, prefer the one that's non-transient. Otherwise, a transient connection could prevent us from opening streams even if we have a second non-transient connection through a better relay.
-
- 19 Feb, 2021 1 commit
-
-
Aarsh Shah authored
-
- 18 Feb, 2021 1 commit
-
-
Aarsh Shah authored
* support for forced direct connections.
-
- 17 Feb, 2021 4 commits
- 19 Dec, 2020 1 commit
-
-
Marten Seemann authored
-
- 05 Jun, 2020 1 commit
-
-
Raúl Kripalani authored
Co-authored-by: Aarsh Shah <aarshkshah1992@gmail.com> Co-authored-by: Raúl Kripalani <raul@protocol.ai>
-
- 20 May, 2020 1 commit
-
-
Aarsh Shah authored
* Rank dial addresss.
-
- 15 May, 2020 1 commit
-
-
Aarsh Shah authored
-
- 01 Apr, 2020 1 commit
-
-
Will Scott authored
-
- 31 Mar, 2020 1 commit
-
-
Steven Allen authored
Otherwise, we can modify the context after/while the process is shutting down. fixes #189
-
- 10 Feb, 2020 1 commit
-
-
Adin Schmahmann authored
only cancel dials when an outbound connection succeeds. this may result in duplicate connections, but it's better to have two connections than dropping both of them and ending up with zero connections.
-
- 04 Nov, 2019 1 commit
-
-
Steven Allen authored
1. Always return the caller's context error if relevant. 2. Don't return "context canceled" when we're just shutting down. 3. Don't claim that the context deadline has been exceeded when the dial timeout is canceled.
-
- 06 Jun, 2019 1 commit
-
-
Steven Allen authored
Avoid logging about closed listeners, etc., when shutting down.
-
- 04 Jun, 2019 1 commit
-
-
Jakub Sztandera authored
License: MIT Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
-
- 03 Jun, 2019 1 commit
-
-
Jakub Sztandera authored
This can be quite an overhead in cases of high connection rates. The main overhead is thread blocking syscall causing a lot of context switching. License: MIT Signed-off-by: Jakub Sztandera <kubuxu@protonmail.ch>
-
- 26 May, 2019 1 commit
-
-
Raúl Kripalani authored
-
- 10 Apr, 2019 2 commits
- 19 Feb, 2019 1 commit
-
-
Matt Joiner authored
This reverts commit 3dded3dc.
-
- 15 Feb, 2019 2 commits
-
-
Matt Joiner authored
-
Matt Joiner authored
-
- 28 Aug, 2018 2 commits
-
-
Cole Brown authored
-
Cole Brown authored
-
- 26 Jun, 2018 2 commits
-
-
Steven Allen authored
The global per-peer dial timeout had a significant drawback: When dialing many peers, this timeout could cause libp2p to cancel dials while they were still stuck in the limiter. A better but more complicated approach is a time budget system but we can implement that later. This change simply applies the limit to each `DialPeer`/`NewStream` call independently and makes it easy to override. While old timeout tried to account for how much we're willing to spend dialing a single peer, this new timeout tries to account for the amount of time a single "client" is willing to wait for a dial to complete before they no longer care.
-
Steven Allen authored
-
- 07 Jun, 2018 1 commit
-
-
Łukasz Magiera authored
-
- 05 Jun, 2018 1 commit
-
-
Steven Allen authored
Removes: * go-libp2p-conn logic (moved to transports) * go-libp2p-peerstream (moved here) Changes: * New transport interface. * Explicit over implicit (the implicit automagic now all lives in go-libp2p): * No more default transports, muxers, etc. * No more fallback dialer. Transports are now *required*. * Stream opening: * Connection picking logic (instead of just picking the first). * Tries harder to open a stream of some connections happen to be closed. * Stream closing: * No longer treats half-closed streams as fully closed. Users *must* read the an EOF or reset the stream for it to be garbage collected. * No more polling for dead connections. * Multiplexers are now *non-optional*. Really, they haven't been optional for a while but we still pretended that they were. * No more Network type alias. It added a bunch of code and didn't really provide anything but an alternative set of methods that do the same thing. * Notifications: * New guarantee: connection open notifications will complete before connection close notifications begin. * Given that, notifications are now delivered in parallel. No more notification backlogs blocking connection closing/opening.
-
- 06 Dec, 2017 1 commit
-
-
Steven Allen authored
We call this method in `FindProvidersAsync`. Really, we shouldn't even be doing that (but this is "good enough" for now).
-
- 14 Nov, 2017 1 commit
-
-
Steven Allen authored
It doesn't exist anymore. This is now handled entirely though contexts.
-