Closed mcollina closed 9 years ago
i dunno.
what do you think the libchan expected behaviour around this would be? Since the behaviour currently seems undefined by the spec, I just worry about doing something here that goes counter to what the spec becomes.
It's definitely what we want to happen on the graft side of things though.
are there situations where you would explicitly not want this, or the automatic 'fix' is going to get in the way?
I spoke too early. It's missing ByteStream support :(
Ok, now is done :dancers:
Currently a channel, once created, can be serialized only within the session that has originated it.
This means that I cannot route the messages between the services easily, i.e. I cannot send a channel from one user to another client. Currently, this can be done only through explicit piping.
However, I think it's doable to automatic 'fix' this, so when we send a channel bound to another session, it gets automatically piped. What do you think?