At the moment the first socket to send a message to the mix is labeled as the mix-socket and all responses are sent to it, no matter where the requests where coming from, initially.
It should be the case, that a channel id is associated with a socket and only requests from this socket are accepted and responses on this channel are only sent to this socket.
This way more than one client can send messages to the first mix. The other mixes should not be troubled by the open sockets, since there is still link encryption.
At the moment the first socket to send a message to the mix is labeled as the mix-socket and all responses are sent to it, no matter where the requests where coming from, initially.
It should be the case, that a channel id is associated with a socket and only requests from this socket are accepted and responses on this channel are only sent to this socket.
This way more than one client can send messages to the first mix. The other mixes should not be troubled by the open sockets, since there is still link encryption.