Automatic object stream piping about jschan HOT 5 OPEN

Hey @mcollina can you elaborate with some (pseudo) code?

from jschan.

So you might want to use a https://www.npmjs.org/package/from2 fro generating some events to pop to a client.

Right now you have to do:

session.on('channel', function(chan) {
  chan.on('data', function(msg) {
    var chan = chan.WriteChannel()
    from2(...).pipe(chan)
    msg.returnChannel.end({
      more: chan,
      error: false
    })
  })
})

Using graft syntax:

through.obj(function(msg, enc, done) {
    var chan = msg._channel.WriteChannel()
    from2(...).pipe(chan)
    msg.returnChannel.end({
      more: chan,
      error: false
    })
})

However, with this you might want to use:

through.obj(function(msg, enc, done) {
    msg.returnChannel.end({
      more: from2(...),
      error: false
    })
})

and it gets automatically piped.

This would also greatly help seneca integration, as at that point it could just forget about channels.

The only point will be Transform streams, which must get an isReadChannel or isWriteChannel property hooked up.

from jschan.

could we abstract the pain by doing the channel switching under the hood in response to a pipe event?

from jschan.

deja vu? #22

from jschan.

@AdrianRossouw this is the missing bit for #22. However it requires some changes to msgpack5.

@davidmarkclements for sure! This requires some changes to msgpack5, if you want to help we can discuss the details there.

from jschan.