Add MemoryPool<byte> to ConfigurationOptions for the BufferedStreamWriter (CycleBuffer or PipeOptions) v3

[pairbit]

I need to specify my MemoryPool when making a Redis request.

[mgravell]

Seems reasonable, but out of curiosity: what is the concern here?

[mgravell]

to clarify my question: in order to ensure we're solving the right problem in the right way, it would be great to have a solid understanding of what the reasons are; for example, is this for performance? security/isolation? other? And if security is a factor: there may be other pool scenarios we'd want to consider, for example avoiding the shared array pool

[pairbit]

I use isolated pools based on BoundedConcurrentQueue. This ensures memory control and security.