On Thu, Apr 29, 2010 at 5:40 AM, roger peppe <rogpe...@gmail.com> wrote:
> what happens if the consumer is slow and the Rstream writer > blocks? how do you stop all the other replies on the connection > waiting for the consumer to get on with it? there are not replies -- the rstream is a reply. If the consumer is slow packets are lost. That's life. > > in fact, how do you stop it deadlocking if the consumer is in > fact waiting for one of those replies? ?? One Tstream. Lots of Rstreams. Zero interaction. > i suppose this comes down to what the API looks like. > isochronous might be easier, as a slow reader is a bad reader > so you could just throw away some data. Yes. ron
