Under the hood, we're basically using the HttpWebRequest class whose input is now an unbounded System.IO.Stream instead of a man-in-the-middle MemoryStream.
Although the latter does simplify code and we still use this code path if the file we're uploading is small enough, it is obviously an inefficient use of memory and an OOM trigger if we're trying to upload a file that's several GBs in size. So yes it's feasible. Our API just expects a System.IO.Stream. We don't care whether it's a file, in-memory object, or a download data stream from a remote cloud service/provider. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/MapGuide-Maestro-5-0-RC1-and-4-0-5-maintenance-release-available-tp5056482p5056592.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
