Fernando,
You should be alright if you are using GetResponseStream. It should
allow you to call ReadToEnd on the stream and get the result.
If you were using a NetworkStream though, it's different, as you can
send say, 32 over the wire (a space), but still have a connection, so the
stream is not complete yet. If you called ReadToEnd on that, then it would
wait for all of the bytes, and then for the stream to close, and therefore,
block.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Fernando Rodríguez" <fe*******************@fernando-rodriguez.com> wrote in
message news:04********************************@4ax.com...
On Mon, 18 Oct 2004 13:24:14 -0400, "Nicholas Paldino [.NET/C# MVP]"
<mv*@spam.guard.caspershouse.com> wrote:
Fernando,
If you know the encoding for the stream, just wrap the stream in a
StreamReader, and call the ReadToEnd. Be careful if you are reading from
a
network stream, as this will cause it to hang if the stream is not
disconnected when done (as opposed to reading messages from the stream and
keeping it open).
Actually it's the return value of HttpWebResponse.GetResponseStream().
I'm afraid that what I need is a better understanding of Streams. Could
you
point out some tutorial that cover streams and specifically network
streams?
O:-)
TIA