The best way to handle such behaviors is to create a Javascript
process on the client side that requests regularly the server.
Connections can be maintained, for example :
public function executeNotifyUpdate()
{
$max = 50;
while (!$this->hasChanged() && $max-- > 0)
{
usleep(100);
}
$this->getResponse()->setContent($this->hasChanged() ? 'changed'
: 'unchanged');
return sfView::NONE;
}
Le 10/08/10 15:29, Cristian Baciu a écrit :
Hi guys,
thanks for suggestions but I need a solution without java script.
I think this is a limitation of the implementation of the MVC pattern
in symfony2. We should be able to start the output to the client in
any moment not only at the end of the "action".
Kind Regards,
Cristian
--
---
Alexandre Salomé - http://alexandre.salome.fr
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
