Why is the workflow management system integrated?

Next topic

Author	Message
Clemens T	Saturday 25 April 2009 8:19:12 am Hello all, I was wondering why eZ Systems has integrated a workflow system into eZ Publish? The reason for that seems obvious: to manage workflows. But wouldn't it be much better if this workflow system would have eZ Publish as a running process that it maintains? Since then you would have separation of concerns and it will be easier to integrate other software to work with eZ Publish. Regards, Clemens

Author

Message

Saturday 25 April 2009 8:19:12 am

Hello all,

I was wondering why eZ Systems has integrated a workflow system into eZ Publish? The reason for that seems obvious: to manage workflows. But wouldn't it be much better if this workflow system would have eZ Publish as a running process that it maintains? Since then you would have separation of concerns and it will be easier to integrate other software to work with eZ Publish.

Regards,
Clemens

eZ debug

Timing:	Jan 19 2025 00:28:23
Script start
Timing:	Jan 19 2025 00:28:23
Module start 'layout'
Timing:	Jan 19 2025 00:28:23
Module start 'content'
Timing:	Jan 19 2025 00:28:23
Module end 'content'
Timing:	Jan 19 2025 00:28:23
Script end

Main resources:

Total runtime	0.8385 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0051	588.0625	152.6406
Module start 'layout'	0.0051	0.0031	740.7031	39.4766
Module start 'content'	0.0083	0.8285	780.1797	399.7031
Module end 'content'	0.8368	0.0016	1,179.8828	8.1250
Script end	0.8384		1,188.0078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.3837	16	0.0002
Check MTime	0.0013	0.1607	16	0.0001
Mysql Total
Database connection	0.0007	0.0872	1	0.0007
Mysqli_queries	0.8017	95.6164	46	0.0174
Looping result	0.0004	0.0537	44	0.0000
Template Total	0.8061	96.1	2	0.4030
Template load	0.0023	0.2697	2	0.0011
Template processing	0.8038	95.8674	2	0.4019
Template load and register function	0.0002	0.0187	1	0.0002
states
state_id_array	0.0009	0.1082	1	0.0009
state_identifier_array	0.0009	0.1020	2	0.0004
Override
Cache load	0.0016	0.1909	7	0.0002
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0782	1	0.0007
Fetch class attribute name	0.0006	0.0734	1	0.0006
XML
Image XML parsing	0.0001	0.0109	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0005	1	0.0000
General
dbfile	0.0007	0.0872	10	0.0001
String conversion	0.0000	0.0011	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 6 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs