#dat

mafintosh: is there any good reason not to add support for objectMode streams to multiplex?

juul: not sure what you mean by that

it seems that multiplex only deals in binary, so if i want to pass a stream through multiplex and it's a utf8 stream then it comes out the other end as binary

and if I try to send an object then it fails

it would be cool if I could use it for binary streams, but if I used multiplex.createStream(myId, {objectMode: true}) or multiplex.createStream(myId, {encoding: 'utf8'}) then it would deal with that

maybe I should just implement a small wrapper library?

it would be easy to send the information about what type of stream is being created using the createStream id argument, such that the other end can use StringDecoder and JSONStream.parse as needed

but that functionality could also be part of multiplex itself

so I guess I'm asking: which would you prefer

juul: it should be separate

juul: you can use stream.setEncoding('utf-8') - thats part of streams

mafintosh: doesn't seem to have an effect on streams created with multiplex.createStream

juul: i meant you need to call set encoding on the stream returned from .createStream :)

mafintosh: http://pastebin.com/rhs9YzCA

am I missing something obvious?

juul: you need through.obj

doh

thanks

juul: np

juul: if you want to send json you can use https://github.com/mafintosh/duplex-json-stream if you to wrap the multiplex channels

it probably has the best source code of all my modules

nice!