You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The design initially aimed to facilitate a thumbnail feature for channels, with the first version of the protocol kept as simple as possible. However, this protocol has evolved over time.
The first round of improvements was spearheaded by @devos50, following his experiment with large-scale binary model transfers for distributed machine learning experiments (#6831). This enhancement also incorporated a bug fix identified by @rmadhwal and detailed in trustchain-superapp issue #101.
The next set of refinements was led by @kozlovsky in #6845, following his review of #6831.
A possible future enhancement is enabling concurrent transfers to the same peer, as discussed in #7074 (comment), #7258 (comment). Until now, this feature wasn't a priority in Tribler, given the lack of substantial demand for simultaneous binary transfers to the same peer. However, the time may be right to reconsider this?
It's also important to note that the Python EVA and Kotlin EVA have different implementations and are likely incompatible as of now.
The text was updated successfully, but these errors were encountered:
EVA protocol is a binary data transfer protocol based on TFTP with window size (RFC 7440) implemented on top of the ipv8 networking layer.
The design initially aimed to facilitate a thumbnail feature for channels, with the first version of the protocol kept as simple as possible. However, this protocol has evolved over time.
The first round of improvements was spearheaded by @devos50, following his experiment with large-scale binary model transfers for distributed machine learning experiments (#6831). This enhancement also incorporated a bug fix identified by @rmadhwal and detailed in trustchain-superapp issue #101.
The next set of refinements was led by @kozlovsky in #6845, following his review of #6831.
A possible future enhancement is enabling concurrent transfers to the same peer, as discussed in #7074 (comment), #7258 (comment). Until now, this feature wasn't a priority in Tribler, given the lack of substantial demand for simultaneous binary transfers to the same peer. However, the time may be right to reconsider this?
It's also important to note that the Python EVA and Kotlin EVA have different implementations and are likely incompatible as of now.
The text was updated successfully, but these errors were encountered: