.Net异步套接字操作限制？(.Net asynchronous socket operations limit?)

 待处理的异步操作是否应该谨慎使用？ 
 
 我有一大堆连接的TcpClients，我不期待输入，但为了防止一个行为不端，我需要保持输入缓冲区为空。 如果每个连接的客户端都有一个BeginRead（），它会无限期地保持打开状态，那有什么危害吗？ 当客户端最终关闭时将调用回调，如果！asyncResult.IsCompleted我可以退出它。 
 
 我不知道开始阅读多少字节，但我相信我可以共享一个缓冲区。 输入到缓冲区限制可能只是在流中，未读。 有没有更好的方法来有效地丢弃，禁止或等待流中数据的可用性？ 
 
 否则我需要轮询可用的数据。 
 
 谢谢！ 

Are pending asynchronous operations are precious resource that should be used sparingly?
 
I have a slew of connected TcpClients that I'm not expecting input from, but just in case one is misbehaving, I need to keep the input buffers empty. If I have a BeginRead() for each connected client that just stays open indefinitely, is there any harm? The callback will be called when the client is eventually closed and I can just return out of it if !asyncResult.IsCompleted.
 
I wouldn't know how many bytes to begin reading, though I believe I could share one buffer. Input up to that buffer limit could just sit in the stream, unread. Is there a better way to efficiently discard, disallow, or WAIT on the availability of data in a stream?
 
Otherwise I need to poll for data available.
 
Thanks!

原文：https://stackoverflow.com/questions/5143716