Thanks for "Custom Resource Type How-To", great documentation. We expect our custom doctype(s) instances to be rather large, while the XML<->XHTML mapping is straightforward and does not require random access. Thus, i was wondering if we can eliminate in-memory tree creation at least for views instead of aggressively exploring caching mechanisms.
I was wondering if Lenya creates an in-memory representation for internal purposes during the execution of "view" pipelines? Also, can i associate SAX Transformers per doctype instead of XSLT? We are going to use a number of doctypes so i would like this to be manageable, somewhat like the naming conventions used for the traditional (XSLT) way. Any advice much appreciated! Manos --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
