Why did ez choose to implement their own XML parser?

«

Previous topic

|

|

Next topic

»

Author

Message

Wednesday 30 July 2003 10:01:47 pm

Hi all,

Why did ez choose to implement their own XML parser?

--vasu

Wednesday 30 July 2003 11:35:58 pm

We used to use libxml. But this parser had severe memory leaks at the time and was not working in a production environment. It also had a hard time parsing some very valid XML files.

We then made an extension to PHP for supporting the QT, qdom, C++ XML parser. This worked well, however people had a hard time installing this.

So to make eZ publish simpler to install we made an XML parser which is bundled with eZ publish.

--bård

Documentation: http://ez.no/doc

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 31 2025 04:15:54
Script start
Timing:	Jan 31 2025 04:15:54
Module start 'layout'
Timing:	Jan 31 2025 04:15:54
Module start 'content'
Timing:	Jan 31 2025 04:15:54
Module end 'content'
Timing:	Jan 31 2025 04:15:54
Script end

Main resources:

Total runtime	0.0148 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	588.2813	151.2266
Module start 'layout'	0.0054	0.0028	739.5078	36.6797
Module start 'content'	0.0082	0.0050	776.1875	90.0938
Module end 'content'	0.0132	0.0015	866.2813	29.9922
Script end	0.0147		896.2734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	17.8104	14	0.0002
Check MTime	0.0011	7.5397	14	0.0001
Mysql Total
Database connection	0.0008	5.4733	1	0.0008
Mysqli_queries	0.0027	18.4088	3	0.0009
Looping result	0.0000	0.0952	1	0.0000
Template Total	0.0012	7.9	1	0.0012
Template load	0.0009	6.1637	1	0.0009
Template processing	0.0003	1.7535	1	0.0003
Override
Cache load	0.0007	4.5199	1	0.0007
General
dbfile	0.0013	8.8834	8	0.0002
String conversion	0.0000	0.0548	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs