Open cbaxter opened 12 years ago
What do you mean "should not be able to intermix bind and send calls on same channel"?
I was debating if you would mix listeners and connections within the same channel instance:
i.e., DuplexChannel channel; channel.Bind("tcp://127.0.0.1:5555"); channel.Connect("tcp:127.0.0.1:6666");
There will be nothing preventing you from doing so; just was not sure if it made sense.
Oh, I think you meant to type "bind and connect" instead of "bind and send". I get it now.
I agree that it doesn't make sense to Bind and Connect on the same channel instance. Doing so might be an indication that you're trying to bridge two networks, which we can optimize for with an explicit Bridge interface (similar to Zmq devices).
Yes, that would have been a typo. Corrected.
Elevating priority; required to clean-up endpoint implementation and will influence issues like Issue #22.
Allow for multiple bindings or connect calls on a single channel to various end points. Should be able to bind multiple endpoints such as TCP/IPC etc through a single channel. Should not be able to intermix bind and connect calls on same channel.