[Mono-dev] Should we replace MemoryStream?
ClassDevelopment at A-SoftTech.com
Mon Nov 9 14:41:54 EST 2009
Are you talking about System.IO.MemoryStream?
Then imho this would be a problematic move.
Most people are used to new MemoryStream (someByteArray) being O(0) time,
but with ChunkedStream would be O(n). In fact in those cases ChunkedStream
would need twice the memory because it would still need to retain the
original byte array (e.g. for GetBuffer).
Von: mono-devel-list-bounces at lists.ximian.com
[mailto:mono-devel-list-bounces at lists.ximian.com] Im Auftrag von Miguel de
Gesendet: Montag, 9. November 2009 19:10
Betreff: [Mono-dev] Should we replace MemoryStream?
I just blogged about a memory fragmentation issue here:
And I am wondering: since MemoryStream is one of these sources of
problems, we could replace this implementation with MindTouch's
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list