• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

XSL/XSLT Shortcomings

 
Ranch Hand
Posts: 170
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi:
If you have worked with XSL/XSLT, you probably like or love it. However, I am wondering if this is one big shortcoming for xsl. When processing huge XML files (1,10,100MB depending on the cituation), the resource usuage and performance problem can become so bad. To me, this originated from the fact that XML has to be parsed in WHOLE before going thru those templates of xsl.
I wonder if this is possible to parse xml in part of some sort of serial fashion so the transformation can be performed like a production line. This would at least save some resources. I am not sure at all if this is feasible.
Of course, you can always chop XML into pieces and do the xslt one by one. But that's quite a different approach and doesn't always work.
Am I making sense here?
-TY
 
reply
    Bookmark Topic Watch Topic
  • New Topic