> > Ahh, perhaps I am starting to get it. Basically the XSLT recipes > configure the processing of the code to use XML libraries, and when you > do an Execute on them, they make the calls using the specified XML > library (libxml2 in my case). So all the XSLT functionality is done > by the respective libraries, and Embperl makes the necessary calls to > these by wrapping these in perl code to conform to the Embperl API. > > So all Embperl really knows is the correct way to call the few necessary > functions from the XML library to parse and get the XSLT done. Nice > > That close? >
Yes, that's what Embperl currently does. Additionaly it caches parsed XSLT stylesheets and XML documents (you can configure that), so when you make a lot of transformations using the same stylesheet on different doucments, the sytlesheet only get's parsed once (Embperl automaticly reparses it when it changes on disk) Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
