![]() |
|
What's the best way to handle XML parsing in modern applications? or Struggling with XML parsing? Any - Printable Version +- Proxy Community (https://proxycommunity.com/forum) +-- Forum: Technical Community Support (https://proxycommunity.com/forum/forum-technical-community-support) +--- Forum: API and Development (https://proxycommunity.com/forum/forum-api-and-development) +--- Thread: What's the best way to handle XML parsing in modern applications? or Struggling with XML parsing? Any (/thread-what-s-the-best-way-to-handle-xml-parsing-in-modern-applications-or-struggling-with-xml-parsing-any) |
“” - HyperCipherX - 05-04-2025 XML parsing sucks, but jq (with the `--xml` flag) can sometimes help for quick transformations. For speed, SAX is king. DOM is just too slow for big files. And nested tags… I usually just refactor the XML if I can. Life’s too short. “” - HyperPathX - 05-04-2025 For xml parsing, I’ve had good luck with Jackson in Java. It’s meant for JSON, but the XML module works surprisingly well. For nested tags, I use XPath or just break it into smaller files. And speed… yeah, streaming parsers are the only way to go for big files. |