InfinityMQ/InfinityMQ — comment on commit a91a0b4607c83cfd3363add680f4c6f2c1fcd95a
File: src/Core/Channels/Framing/Writers/BufferedFrameWriter.cs line 32
By cbaxter:

Also, if anyone has any suggestions on how to make this less weird; it would be appreciated. When Write is called, you pass in the stream that you want to write to. The objective was to not have to tear down and rebuild the frame reader/write for the future reconnect scenario. Thus you pass in the stream that you want to write on. However, with the buffered reader/writer you are deferring the write to a future async operation so we are just grabbing the stream that will be written to in the future. Feels a little dirty; so any input/thoughts would be appreciated.

NOTE: Given the larger buffer sizes (i.e., 1MB byte array); recreating repeatedly if you are having intermittent connectivity issues wont be GC friendly.