Hi Angelo Altough I did try the multi fragment approach, some people also suggested looking into stx transformer , and indeed, my stx pipeline is faster because the incoming document start being processed as soon as it is being generated by the previous component, as opposed to xslt that need to wait that the whole input document loads in memory.
I found stx more general than multifragment and it allows one to save elements during the processing, so it's theorically possible to do everything you could do in xslt in stx. But using stx (it's an event based adaptation of xslt) requires rethinking you transformer. It works great when you deal with a long monotonous list of element that can be processeed individually, it requires a bit more planning and you must put a bit more effort in stx to create a efficient transformation -- the sequence of element in the input document is very important for stx. I don't know if this will help with your problem, I suggest you peek at stx specs http://stx.sourceforge.net/ and decide by yourself. Hope it helps. Eric -----Message d'origine----- De : Angelo Immediata [mailto:[EMAIL PROTECTED] Envoyé : 6 novembre, 2005 05:11 À : Help Cocoon Objet : Increasing Cocoon Portal speed Hi all. First of all i'm sorry for being so discontinuous in following this thread, but i'm very busy in the project i'm following. However i have read this thread: http://www.mail-archive.com/[email protected]/msg30344.html where there has been a solution for processing large file and increasing the performance.... May us use this approach in order to process large layout and copletinstancedata xml files? What about this way?Or have you thinked about anything else? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
