<br>Ben,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
> So does that mean that when a consumer wants to perform a channel.flow,<br>
> there will be a call made available on the channel, say<br>
> amqp_channel:flow(true|false)? Otherwise, if the consumer sends a<br>
> channel.flow command directly, it is inconsistent on an API level with the<br>
> producer, which only receives pause and resume atoms. (a) Do you agree and<br>
> (b) How do you plan to handle that side of it?<br>
<br>
</div>ATM the client can't initiate a channel.flow command, only the broker<br>
(I mentioned this in the article).<br>
<font color="#888888"></font></blockquote><div><br>I have to be really careful how I ask you questions, I can see that :)<br><br>I should have phrased it like this, I suppose: How do you envisage the consumer application will call the client when the client DOES support initiating a channel.flow command?<br>
<br>Ed.<br></div></div><br>