3

Suppose that your application serializes objects using XmlSerializer. When another part of the application (e.g. an external service or another component) process that XML file, gets you back a huge XML file that is a serialization of a huge object.

Which are your approach in deserializing and processing that response without filling your server's memory?

I usually prefer to use the XmlSerializer, but when I have to fight against these monster, I have no bullet-proof solutions. I've read about XNode.ReadFrom, but I'm wondering if using this method I can accomplish like a streaming-deserialization.

Mark Rotteveel
  • 100,966
  • 191
  • 140
  • 197
Marconline
  • 1,108
  • 12
  • 30

0 Answers0