The number of iterations cooresponds to the number of rows returned from the database. There are roughly 46,000 rows present now, so I need at least that many rows in my display. The XSL design enables me to use SAX which should help. The easiest thing would be to limit the number of rows returned to something more reasonable like 10,000 (or up the JVM memory :P), but this is the requirement I'm stuck with.
Help me understand this: If I apply a transformation using XSLT, streaming the xml in, does Cocoon "stream" the results out? IE, does the entire transformation happen in memory and then get flushed to the client, or does Cocoon flush the buffer to the client as xxx bytes are filled? I made an assumption that Cocoon does this automatically.
If anyone else has any suggestions, please let me know. TIA,
Tom
Bertrand Delacretaz wrote:
Le 19 nov. 04, � 02:45, Tom Bloomfield a �crit :
...The XML I will be processing will be 10-12 MB in size, and will grow from there. Based on planning, the XSL will contain around 50 node traversals and will iterate over my XML dataset around 46,000 times....
You'll probably have a hard time doing this on a 256-MB system.
In such a case I'd ask myself if my problem is *so* hard as to require 46'000 iterations over the XML dataset. Of course it depends on the kind of data you're processing, but this sounds very unusual.
-Bertrand
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
