Request filter, filter chain or comparable solution

Next topic

Author	Message
Tobias Vogel	Tuesday 01 July 2008 8:48:02 am Hello, a concept which i know from the PHP Application Framework Symfony, or from J2EE web solutions, is the introduction of request filtering and a filter chain. Basically, these are classes with a function, that gets called on every request and gets handed over request parameters. A short description on how this might work can be found here (symfony docs): http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer#Filters Besides security measures, this can be very useful to dynamically insert code into the pagelyout (Google Analytics and others come to mind). With this method, one can keep the pagelyout and/or templates very clean and put the logic into a filter class and easily reuse it. Is there something comparable, when developing with eZ Publish or is someone aware of an alternative solution?

Author

Message

Tuesday 01 July 2008 8:48:02 am

Hello,

a concept which i know from the PHP Application Framework Symfony, or from J2EE web solutions, is the introduction of request filtering and a filter chain. Basically, these are classes with a function, that gets called on every request and gets handed over request parameters. A short description on how this might work can be found here (symfony docs):

http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer#Filters

Besides security measures, this can be very useful to dynamically insert code into the pagelyout (Google Analytics and others come to mind). With this method, one can keep the pagelyout and/or templates very clean and put the logic into a filter class and easily reuse it.

Is there something comparable, when developing with eZ Publish or is someone aware of an alternative solution?

eZ debug

Timing:	Jan 18 2025 17:58:09
Script start
Timing:	Jan 18 2025 17:58:09
Module start 'layout'
Timing:	Jan 18 2025 17:58:09
Module start 'content'
Timing:	Jan 18 2025 17:58:09
Module end 'content'
Timing:	Jan 18 2025 17:58:09
Script end

Main resources:

Total runtime	0.0216 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.0076	588.0469	152.6406
Module start 'layout'	0.0076	0.0027	740.6875	39.4922
Module start 'content'	0.0103	0.0092	780.1797	85.1641
Module end 'content'	0.0195	0.0021	865.3438	30.3047
Script end	0.0216		895.6484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	12.5996	14	0.0002
Check MTime	0.0013	5.8811	14	0.0001
Mysql Total
Database connection	0.0009	4.3507	1	0.0009
Mysqli_queries	0.0032	14.9542	3	0.0011
Looping result	0.0000	0.1434	1	0.0000
Template Total	0.0017	7.6	1	0.0017
Template load	0.0009	4.2491	1	0.0009
Template processing	0.0007	3.3742	1	0.0007
Override
Cache load	0.0007	3.0222	1	0.0007
General
dbfile	0.0043	19.9206	8	0.0005
String conversion	0.0000	0.0552	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