Approach (an adaptor for each way? a duplex? ...?)

[Fishrock123]

Heya @mcollina, @mafintosh

I've made two base classes, assuming that would be the easiest to start from.

I guess in the future a duplex might be the simplest adaptor? Not sure.

I don't really know how to integrate the pull-y-ness into the regular streams3 api though... we probably need to go deep and mess with events and such I guess?

readable-sink.js & writable-source.js

[mcollina]

I would go with a different approach, and completely encapsulate the source and the sink. IMHO our Readable should act as a Sink for Bob, and Writable as a Source. Something like

Source --> ReadableSink --> Readable
Writable --> WritableSource --> Sink

[Fishrock123]

Maybe I wasn't clear, I think that was the same plan as mine.

I do wonder if it should just be one 'duplex' though. Guess we'll find out in time.

[mcollina]

looking at the code, I would structure it differently, not exposing the bind* method directly, but having it as a private helper. Il giorno mer 31 ott 2018 alle 16:43 Jeremiah Senkpiel < notifications@github.com> ha scritto:

…

Maybe I wasn't clear, I think that was the same plan as mine. I do wonder if it should just be one 'duplex' though. Guess we'll find out in time. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADL42stQQxx0Kj76EbrNyARpeo8wB2Kks5uqdM6gaJpZM4YCgwO> .