Bug #15249 Updated: xslt processor accepting dom object
| From: | chregu@php.net | Date: | Mon, 28 Jan 2002 08:00:22 +0000 |
| Subject: | Bug #15249 Updated: xslt processor accepting dom object | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-78284@lists.php.net to get a copy of this message | ||
ID: 15249
Updated by: chregu
Reported By: r.klinkenberg@student.utwente.nl
Old Status: Open
Status: Closed
Bug Type: Feature/Change Request
PHP Version: 4.1.0
New Comment:
Because the underlying sablotron library does not accept Dom-Objects
(from libxml2) as input, so there's no way to doing it without
serializing in between.
But in PHP 4.2, the domxml extension will have it's own xslt engine,
which accepts Dom-Objects just fine (if someone implements
(gnome-)libxslt-support into ext/xslt, then this is maybe also possible
with the xslt-extension, but not with sablotron...)
Previous Comments:
------------------------------------------------------------------------
[2002-01-27 22:26:49] r.klinkenberg@student.utwente.nl
Recently I discussed the way how xslt is implemented in php with some
java user. We came to the conclusion that there is probably much
overhead in php, since the xslt processor doesn't accept dom object.
When I'm building my xml dynamicly using a dom object, is has to be
serialized to a string before it can be passed to sabletron. That means
that sabletron has to parse that string again to make a dom object out
of it.
To me that looks quitte inefficient. Why not let the xslt processor
accept a dom object? That would probably speed up everything very much.
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=15249&edit=1