[rabbitmq-discuss] FW: Multiple consumers

[Matthias Radestock]

Ben,

"Ben Hood" <0x6e6562 at gmail.com> writes:

> what happens when you have connections to mulitple remotes servers or
> you have one connection via the direct API and another via the
> networked API (e.g. if you were connecting to rabbitmq directly and
> interacting with say QPid remotely)?
>
> Example:
>
> User --> ChannelProcess(N) --> ServerReader/Writer
> User --> ChannelProcess(N) --> Network --> Server
>
> In this example a user has opened channel N using the direct API and
> has opened another channel N with a remote network server. How does
> the user distinguish between the two Pids that they would have to use
> in conjunction with an API call? If you just supplied the channel as a
> parameter, the channel Pid resolution wouldn't work, unless the user
> stores the Pid of the spawned channel process when they start it. Then
> in that case, for the direct API since you have a process per channel,
> you wouldn't even need to supply the channel. You would only need the
> channel in the network case, where you have a single socket handling
> process.

Sorry about the confusion, I meant
  access_request(Channel*Pid*, Realm)
So yes, the user would need to keep hold of the ChannelPid, just as they
currently keep hold of the object reference to the Channel object in the
Java API.

This would work for both the network and direct API.


Matthias.