Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Subject: Re: C# NetworkStream.close() behavior
To: dev@reef.apache.org
References: <CAO2PpvsRZDBKDXZHwdC_S7rag52NeLQx37two8HxLibbu-LfWg@mail.gmail.com>
From: Markus Weimer <markus@weimo.de>
Message-ID: <57598641.4040906@weimo.de>
Date: Thu, 9 Jun 2016 08:07:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAO2PpvsRZDBKDXZHwdC_S7rag52NeLQx37two8HxLibbu-LfWg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Thu, 09 Jun 2016 15:07:57 -0000

On 2016-06-08 18:24, Dhruv Mahajan wrote:
> It seems that even of read==0, there are bytes left to read. My
> understanding on reading the documentation was that no further data
> is available since stream is closed. Any idea where am I going
> wrong?

The documentation[0] states:

> Instead of calling this method, ensure that the stream is properly
> disposed.

So, you might want to use `.Dispose()` instead?

Markus

[0]: 
https://msdn.microsoft.com/en-us/library/system.net.sockets.networkstream.close%28v=vs.110%29.aspx