在同一管道上运行的流的资源处理

发布于 2024-12-22 07:21:02 字数 775 浏览 1 评论 0原文

首先，我写入 NamedPipeClientStream，然后从中读取。这基本上有效。但我没有正确处理 StreamReader 和 StreamWriter 的资源。

方法 1

using (StreamWriter sw = new StreamWriter(pipeStream))
{
  // ...
  using (StreamReader sr = new StreamReader(pipeStream))
  {
    // ...
  }
}

处理 sw 失败，因为流已经关闭。

方法2

using (StreamWriter sw = new StreamWriter(pipeStream))
{
  // ...
}
using (StreamReader sr = new StreamReader(pipeStream))
{
  // ...
}

现在另一个进程中的管道服务器陷入困境，因为管道连接过早关闭。

方法3

在另一个有关文件流的问题中，建议使用Reader 和 Writer 的单独流。但这不能应用，因为两者应使用相同的管道实例。

那么在这种情况下如何正确管理流呢？

原文

First I write to a NamedPipeClientStream, then I read from it. This basically works. But I don't get the ressource handling of the StreamReader and StreamWriter right.

Approach 1

using (StreamWriter sw = new StreamWriter(pipeStream))
{
  // ...
  using (StreamReader sr = new StreamReader(pipeStream))
  {
    // ...
  }
}

The disposal of sw fails, because the stream has already been closed.

Approach 2

using (StreamWriter sw = new StreamWriter(pipeStream))
{
  // ...
}
using (StreamReader sr = new StreamReader(pipeStream))
{
  // ...
}

Now the pipe server in another process struggles, because the pipe connection was closed prematurely.

Approach 3

In another question regarding file streams it was suggested to use a separate stream for Reader and Writer. But this cannot be applied, since both shall use the same pipe instance.

So how are the streams managed correctly in this situation?

分享到QQ

分享到微博