When a template executes an mvt:do into another script repeatedly, does the VM have to reload the script from disk every time?
I'm looking at an application where I need to write a template with an mvt:call, and do some pretty complex processing on the received data. Instead of writing 90 lines of SMT code inside the mvt:call, I thought I might just put an mvt:do in the body of the mvt:call, and the complex processing can be done by a function in a module. But it occurred to me that that might be very slow, because the template would execute the mvt:do for every tag in an XML feed. What say ye, gurus?
Thanks --
I'm looking at an application where I need to write a template with an mvt:call, and do some pretty complex processing on the received data. Instead of writing 90 lines of SMT code inside the mvt:call, I thought I might just put an mvt:do in the body of the mvt:call, and the complex processing can be done by a function in a module. But it occurred to me that that might be very slow, because the template would execute the mvt:do for every tag in an XML feed. What say ye, gurus?
Thanks --
Comment