因为JAXP确实只是一个包装器API(无论人们如何使用它)，它无法使用SAX和DOM提供的任意选项。
Because JAXP really is just a wrapper API (no matter how people are using it), it simply can't support every option that SAX and the DOM provide.
换句话说，它指出了技术可能以可怕的方式使用，无论Facebook打算如何真正使用它。
In other words, it points out that the technology can be used in scary ways, regardless of how Facebook actually intends to use it.
这取决于你想要哪些特性，您可以使用将决定哪些类型的解决方案。无论如何它的东西和带负电的东西都会被加分。
So it depends on which features you want that will dictate which sort of solution you can use. Either way has it's plusses and minuses.
它结束了使用太多内存(无论我如何配置它，我不明白)，交换到磁盘的疯狂，跪下给我点小实例。
It ended up using too much memory (no matter how I configured it, which I don't understand), swapping to disk like crazy and brought my little Small instances to their knees.
它结束了使用太多内存(无论我如何配置它，我不明白)，交换到磁盘的疯狂，跪下给我点小实例。
It ended up using too much memory (no matter how I configured it, which I don't understand), swapping to disk like crazy and brought my little Small instances to their knees.
应用推荐