Remove “off-topic” System.IO classes (SafeNetworkStream is actually dangerous-looking) about sharpfilesystem HOT 2 CLOSED

For example, it signals that the connection was reset and that the handle needs to be cleaned up. Code written against streams will expect this behavior to mean that the end of file was reached and it will assume that the bytes read so far represents the entirety of the entity being read.

Here I am meaning to say that when the API returns 0, normal Stream-using code will assume that meant a successful read of the entire entity. Whereas this “safe” wrapper is basically silently truncating the read data.

from sharpfilesystem.

Yes, totally agree. They were already in the IO directory, so it would be logical to namespace them in SharpFileSystem.IO. I think they could be useful in other projects as well. They are also simple enough to keep supporting them. So I think SharpFileSystem.IO instead of SharpFileSystem.Internal.IO is in order.

SafeNetworkStream was used to normalize Socket-based streams in some hacky applications in the past. For networking read 0 can often be handled the same way as IOException (socket was closed). I agree it is dirty. It also isn't in use by any of SharpFileSystem, so I removed it.

from sharpfilesystem.