Intention of deprecation

[vasco-santos]

In the context of ipfs/js-ipfs#1670, we have been refactoring all libp2p codebase to use async await, async iterators, as well as working on general API improvements to have a better and easier to use js-libp2p.

Taking into account that spdy is an outdated protocol, there are no reasons to use it instead of libp2p-mplex and from our knowledge there are no active projects using libp2p-spdy, we have the intention of deprecating libp2p-spdy and use this time in enhancing the important pieces of libp2p.

If anyone is using this module and want to help us refactoring it, so that you and anyone else interested can use it, let us know. We are happy to help with it too

[jacobheun]

cc @libp2p/repos-javascript

[vasco-santos]

cc

@mkg20001 @jacogr @stefanionescu @richard-ramos @fredfortier @lacabra @notadd

[daviddias]

@vasco-santos before deprecating, can you make sure to benchmark spdy vs. multiplex. I remember that spdy was way more performant in the past.

[vasco-santos]

@vasco-santos before deprecating, can you make sure to benchmark spdy vs. multiplex. I remember that spdy was way more performant in the past.

@daviddias I think we would not get really accurate results, since to have the exact same conditions we would need to refactor spdy to leverage all the other changes we did that also improved beformance for mplex

Regarding past performance, do you have any more recent conclusions @jacobheun ?