From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 29 Apr 2010 10:22:37 -0400
To: 9fans@9fans.net
Message-ID: <43de5c2167c0a4851aeafaa07a0b982d@kw.quanstro.net>
In-Reply-To: <z2gdf49a7371004290540g29060151k700bac13f78f34dc@mail.gmail.com>
References: <5fa9fbfe115a9cd5a81d0feefe413192@quintile.net>
	<Pine.BSI.4.64.1004280750270.14121@malasada.lava.net>
	<4fa1305e0f56a0ef89c2e05320fa5997@coraid.com>
	<t2y13426df11004281142j3c735545k690dcfae6166cd4d@mail.gmail.com>
	<z2gdf49a7371004290540g29060151k700bac13f78f34dc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] A simple experiment
Topicbox-Message-UUID: 125106b2-ead6-11e9-9d60-3106f5b1d025

> 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?

the tcp window closes. and the producer blocks.

> in fact, how do you stop it deadlocking if the consumer is in
> fact waiting for one of those replies?

i don't think i understand this.

i think Tstream would be very dependant on the
transport layer.  that's the part that makes me nervous.
all the world's a tcp?

- erik