>>
>> information). It would be nice if the writer could say "hey, I am
>> still working
>> here but have no data for you. Call me in a bit".
>
In this whole discussion, I've sort of ruled out the possibility of
having the channel poll
nsIStreamWriter. However, would this really be a bad way to go? Upon
finding that
there is no data to read, but that there soon will be, the channel could
sleep for say
100 milliseconds (or some short period of time) and then requery the
writer for data.
We could surely make this delay a configurable parameter. But, somehow
this just
doesn't feel right. Obviously, it would result in wasted time and small
delays for the
user... perhaps even accumulated large delays if the timeout is required
with any
degree of frequency. So, this is probably _never_ the right thing to do.
At any rate, I'm just throwing this out to see what people think.
Darin
