Hi,
>
> But I'd also like to be able to handle xml files, for example, by having
> Execute('*') either use an XML/XSLT Syntax module or invoke another
> apache handler to render the page, and then have it included within the
> EmbperlObject composite output.
Embperl 2.0 will support to include anything that is generated via Perl,
also it will include an XML parser and a XLST engine, so you are able to
include the output of them too. In general you will be able to plugin a
module, and Embperl will be able to use it's output as source. Embperl 2.0
will also be able to pipe the source thru more then one handler, like
filters.
What can't be done with Apache 1.3 is to use the output of any other
_Apache_ (not Perl) module, like mod_php, and feed it into Embperl. This is
because of the internal design of Apache, which always sends the output
directly to the browser. Apache 2.0 will provide an API to capture the
output of any module and when Apache 2.0 is out I will use this, so you can
also use the output of other Apache modules as source.
But what you can do is to extent/change your syntax of your Embperl pages.
I hope to release the 2.0b2 in about two weeks, which will include most of
the stuff that let you define your own syntax. For the 2.0b3 I plan to
include the XML/XSLT stuff.
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]
