BufferManager Class
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Many Windows Communication Foundation (WCF) features require the use of buffers, which are expensive to create and destroy. You can use the BufferManager class to manage a buffer pool. The pool and its buffers are created when you instantiate this class and destroyed when the buffer pool is reclaimed by garbage collection. Every time you need to use a buffer, you take one from the pool, use it, and return it to the pool when done. This process is much faster than creating and destroying a buffer every time you need to use one.
public ref class BufferManager abstract
public abstract class BufferManager
type BufferManager = class
Public MustInherit Class BufferManager
- Inheritance
-
BufferManager
Remarks
This class is commonly used while implementing custom encoders or custom transport channels.
Constructors
BufferManager() |
Initializes a new instance of the BufferManager class. |
Methods
Clear() |
Releases the buffers currently cached in the manager. |
CreateBufferManager(Int64, Int32) |
Creates a new BufferManager with a specified maximum buffer pool size and a maximum size for each individual buffer in the pool. |
Equals(Object) |
Determines whether the specified object is equal to the current object. (Inherited from Object) |
GetHashCode() |
Serves as the default hash function. (Inherited from Object) |
GetType() |
Gets the Type of the current instance. (Inherited from Object) |
MemberwiseClone() |
Creates a shallow copy of the current Object. (Inherited from Object) |
ReturnBuffer(Byte[]) |
Returns a buffer to the pool. |
TakeBuffer(Int32) |
Gets a buffer of at least the specified size from the pool. |
ToString() |
Returns a string that represents the current object. (Inherited from Object) |
Applies to
.NET
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기