The memory footprint depends on the application goals and size really,
but if you're trying to create something simple the chances are you've
got a problem in the materialisation of queried database objects in
the doctrine layer or in your action logic.
Can you be more specific about your set-up
Glad I could help.
On Sep 11, 5:38 pm, Thomas Parisot // Oncle Tom tho...@oncle-
tom.net wrote:
Thanks, you headed us on the good way.
We indeed connected on the `template.filter_parameters` and checked if
the parameter 'sf_content' was there and filled.
:-)
On Sep 11, 4:35 pm, aalexand
Hi,
$sf_content is stored in the attribute holder of the rendered view
rather than the request.
as far as I can see the use of the sfView object is local to the
sfRenderingFilter, which means that you cannot access the appropriate
attributeHolder directly from any other than the
For the sake of clarity I should perhaps also note this - using the
event handler you will only get access to the parameters you
explicitly set in the actions, not the actual sf_content (which holds
the html of the rendered template).
On Sep 11, 3:59 pm, aalexand alexander.s.alexand...@gmail.com
As PHP doesn't support multi-threading, you cannot execute parallel
activities in a single request. I think the most common solution in
this case is to put the task you want to be executed independently in
some kind of message queue (like dropr http://dropr.org), which works
as a separate process
