[mapguide-internals] Patch for Ticket #2432

[Jackie Ng]

Hi John,

I really don't like seeing unbounded System.IO.Stream objects being
funnelled into a MemoryStream. Where possible we always want to leverage the
underlying stream for any API that expects a System.IO.Stream object instead
of copying the contents into a System.IO.MemoryStream and feeding that to
the expecting API. It's a recipe for OutOfMemoryExceptions when you have no
control over the size of the source System.IO.Stream object.

Could you achieve get the same effect if you pass the response object down
to the XmlDataReader or XmlFeatureReader where it can be closed/disposed
when the reader itself is closed/disposed?

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Patch-for-Ticket-2432-tp5135459p5135489.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.