You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially I have a route, which needs to select on two channels. I do this currently simply by having the same IPC channel shared in two different places, one being actually in the same process.
So you end-up with a message struct like:
pubenumBodyChunkRequest{/// This is over IPCChunk,/// Signal the stream is done./// Signal the stream is done(sent from script to script).Done,/// Signal the stream has errored(sent from script to script).Error,}
Note the "script to script" messages. So essentially, some messages are received over IPC, which is the "normal" use-case for the route, but then there are also a few signals that are received from a thread on the same process.
Come to think of it, this is really about being able to add a channel, probably a normal crossbeam channel, to send messages to the route from the same process where it has been setup.
The text was updated successfully, but these errors were encountered:
I'm running into this at servo/servo#26906
Essentially I have a route, which needs to select on two channels. I do this currently simply by having the same IPC channel shared in two different places, one being actually in the same process.
So you end-up with a message struct like:
Note the "script to script" messages. So essentially, some messages are received over IPC, which is the "normal" use-case for the route, but then there are also a few signals that are received from a thread on the same process.
Come to think of it, this is really about being able to add a channel, probably a normal crossbeam channel, to send messages to the route from the same process where it has been setup.
The text was updated successfully, but these errors were encountered: