[WIP] pull-multiplex - pull-streams all the way down

[dignifiedquire]

Current State

• New multiplex implementation using only pull-streams in src/multiplex.js
  • Spec compliant
    • Do not encode the header with a length prefix
    • Check maximum size of data
  • finish destroy method
  • All tests passing
    • Mega stress test, does not run out of memory, but doesn't finish either.
    • Close tests
  • Split into their own package
    • src/pull-end
    • src/pull-split
    • src/multiplex
• Cleanup code
• https://github.com/libp2p/interface-stream-muxer/compare/fix/multiplex?expand=1
• Add documentation

[daviddias]

Have you tested this with the stress tests? Any luck?

[dignifiedquire]

@diasdavid

• stress tests from interface-stream-muxer pass except one error case
• go-libp2p-spdy has problems - Can not send objects to go, if they are larger than 64k js-libp2p-spdy#48 (comment) is the interesting part

[victorb]

Not sure how this file here is relevant, seems to be a demonstration of promises.

[dignifiedquire]

This is super important :P no I just forgot to delete it before comitting, fell free to remove

[victorb]

There is an updated branch based on this work but by using multiplex from npm rather than a re-implementation of the core of multiplex here: #49

[victorb]

pull-wrap branch was merged in 0f3bc8c and exposes a pull-stream interface identical to the one here, but with using multiplex module instead of our implementation.

We'll keep this one open for the future.

[daviddias]

@dryajov now that you are attempting #73, make sure to go through the work @dignifiedquire did here