B
Bryan
Hi,
We have an application that we just upgraded to xerces-c-2_7_0-win32.
This same application used to use xerces-c1_6_0-win32.
We didnt change any other code in our app other than the xerces libs and
dlls that were used.
We are loading up large (>20mb) xml files using DOM (we should use SAX,
I know)- in 1.6 we can parse through the file and pull data on the order
of 10sec. With 2.7, this same parsing takes more than 10 _minutes_!!!!!
I have been scouring the net looking for info, but I am not an xml
expert, nor am I particularly familiar with xerces.
Can any offer any suggestions as to where I might look or clues as to
what might be going on? I found some info on deferred node expansion,
but I really dont know if this can explain this differece.
Thanks,
Bryan
We have an application that we just upgraded to xerces-c-2_7_0-win32.
This same application used to use xerces-c1_6_0-win32.
We didnt change any other code in our app other than the xerces libs and
dlls that were used.
We are loading up large (>20mb) xml files using DOM (we should use SAX,
I know)- in 1.6 we can parse through the file and pull data on the order
of 10sec. With 2.7, this same parsing takes more than 10 _minutes_!!!!!
I have been scouring the net looking for info, but I am not an xml
expert, nor am I particularly familiar with xerces.
Can any offer any suggestions as to where I might look or clues as to
what might be going on? I found some info on deferred node expansion,
but I really dont know if this can explain this differece.
Thanks,
Bryan