Replies: 3 comments 3 replies
-
Do you have a sample program? Note that FORK is not intended to be added directly above the transport, but it is usually the top protocol in a given stack! |
Beta Was this translation helpful? Give feedback.
-
Hi Rob Below's the changed program. Note that it fails at the end when you close the second ForkChannel. You expect that this will change trigger a view change, but it doesn't. A view change will only be triggered when you close one of the main channels (AA or BB). See public class ForkChannelViewAcceptedTest {
} |
Beta Was this translation helpful? Give feedback.
-
You could use only a single channel on each device and do the multiplexing/demultiplexing yourself, e.g. based on a 'topic'. This is actually what ForkChannel provides: the fork-channel-id serves as the muxer/demuxer. So a message is sent to every device, and ForkChannels which don't match the topic drop the message. I'm not sure if I understood your requirements correctly... |
Beta Was this translation helpful? Give feedback.
-
Using ForkChannels with a standard JChannel.
In my case I have multiple, but for this example let's consider just one.
Upon initial creation and connection, the
view_accepted
is called for each channel/cluster. However, once client A and B are established and C joins, A and B will haveview_accepted
called on the main channel but not called on theforkChannel
receiver. C will haveview_accepted
call for both channels.Is this expected behavior? Is this configurable to have the views updated on all channels?
Beta Was this translation helpful? Give feedback.
All reactions