2 ms·
> There's no reason why any file parsing library would end up fetching remote data It's not the API, it is the part of many of the specs, as it was thought to
by acqq 13y ago
> There's no reason why any file parsing library would end up fetching remote data
It's not the API, it is the part of many of the specs, as it was thought to be a good idea once, specifically many standardizations involved additional definitions located at the http servers, example:
http://msdn.microsoft.com/en-us/library/aa468557.aspx http://msdn.microsoft.com/en-us/library/aa468557.aspx
Which was "poised to play a central role in the future of XML processing, especially in Web services where it serves as one of the fundamental pillars that higher levels of abstraction are built upon."
So you had to implement it to be "conforming," and then to avoid overheads as "optimizations." Ironically, "/optimize" feature isn't optimized.
The reason this it's not discovered earlier is that the Visual Studios which contain that option were priced more thousands of dollars (I don't know the what the currently cheapest version containing "/optimize" is -- anybody knows?).