Ok, I understand the need of speed, but there is still something that
worries me. This means that the Canonicalization process depends then on
the way the XML document is in memory. For instance, if I load a XML
document from disk and canonicalize it, or build the same document in
memory from
I'll re-iterate, as long as you use official LibXML2 API, it should
work just fine. Or there is a bug in the LibXML2 code :)
Aleksey
On 3/21/14, 1:06 AM, Frank Gross wrote:
Ok, I understand the need of speed, but there is still something that
worries me. This means that the Canonicalization
Hi,
Actually, I have an additional layer to emulate DOM compliant API over
libxml. In that layer, I have a global list of xmlNsPtr for all
namespaces encountered by the nodes (and referenced in node-ns) of a
single XML document. And for each namespace definition (xmlns:xxx) set
on a node, a
The tradeoff here is speed. Again, if you are using standard LibXML2
API then everything will work as expected. I have no idea why do you
need to create new xmlNsPtr objects - this sounds like a waste of
CPU/memory to me but you might have your reasons. But this also breaks
a few assumptions on
How do you manipulate the XML tree? If you are using official LibXML2
function then I believe this code should work just fine unless there is
a bug in the strings dictionary.
Aleksey
On 3/12/14, 10:28 AM, Frank Gross wrote:
Hi,
I'm getting some trouble to verify a XML signature because the
