I'm working on a CMS that uses velocity template extensively (many thousands of templates), and we're trying to figure out how to avoid reparsing these templates over and over.
First idea... does anyone have experience creating alternate resource cache implementations? I've looked at the basic cache impl that's available, and it seems like I could very easily swap it with an LRU Map to avoid sucking up a lot of memory... we have perhaps hundreds or maybe thousands of templates and couldn't keep them all cached in memory. That could help reduce reparsing on the most heavily used templates. Really though, something like caching the parsed templates (i.e., the AST nodes) to disk or somehow using bytecode generation or something to avoid reparsing my templates every time and make this much more memory friendly... if anyone has any experience or ideas with this, I'd greatly appreciate it. -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
