Hi,
Sorry for the mistake, I took you for a colleague who shares the same last
name, AND this message was intended to be private. I don't know what
happened, I guess if there was a badge for the most inappropriate
contribution to the ML I'd earn it...
Apologies,
Le 10 mars 2013 15:21, "Sebastian Krebs" <krebs....@gmail.com> a écrit :
>
>
>
> 2013/3/8 Maxime Douailin <maxime.douai...@gmail.com>
>
>> Tu aurais du poster sur symfony-users, tu risques de te faire basher...
>>
>> C'est comme ça, "you're a user" !
>>
>> A+
>>
>
> Hi,
>
> Next time I would prefer answers in English, Google Translate is not a
> solution ;)
>
> As far as I understood you recommend, that I ask this on the users-list,
> but the question is about an implementation and the answer may lead to a PR
> ;) It is not a question about how to use it, but because why is it
> implemented the way it is and how it (maybe) can be improved.
>
> Regards,
> Sebastian
>
>
>
>>
>> 2013/3/7 Sebastian Krebs <krebs....@gmail.com>
>>
>>> Hi,
>>>
>>> Just wanted to know (before I open a ticket on github), if there was a
>>> reason, why when I run a process using the process component, the component
>>> takes over the timeout handling himself?
>>>
>>> The problem is, that 'wait()' either never returns, or throws an
>>> exception, but doesn't allow to silently return (with null for example),
>>> when the process is fine, but there is simply no further data.
>>>
>>> What I had in mind was to run several projects separately and poll
>>> theire output sequentially like in
>>>
>>>
>>> while (true) {
>>> $p1->isRunning() and $p1->wait($cb, 0);
>>> $p2->isRunning() and $p2->wait($cb, 0);
>>>
>>> if (!$p1->isRunning() && !$p2->isRunning()) break;
>>> sleep(1);
>>> }
>>>
>>> Regards,
>>> Sebastian
>>> --
>>> github.com/KingCrunch
>>>
>>> --
>>> --
>>> If you want to report a vulnerability issue on Symfony, please read the
>>> procedure on http://symfony.com/security
>>>
>>> You received this message because you are subscribed to the Google
>>> Groups "symfony developers" group.
>>> To post to this group, send email to symfony-devs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> symfony-devs+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/symfony-devs?hl=en
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Symfony developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to symfony-devs+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>> --
>> --
>> If you want to report a vulnerability issue on Symfony, please read the
>> procedure on http://symfony.com/security
>>
>> You received this message because you are subscribed to the Google
>> Groups "symfony developers" group.
>> To post to this group, send email to symfony-devs@googlegroups.com
>> To unsubscribe from this group, send email to
>> symfony-devs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/symfony-devs?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Symfony developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to symfony-devs+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
>
> --
> github.com/KingCrunch
>
> --
> --
> If you want to report a vulnerability issue on Symfony, please read the
> procedure on http://symfony.com/security
>
> You received this message because you are subscribed to the Google
> Groups "symfony developers" group.
> To post to this group, send email to symfony-devs@googlegroups.com
> To unsubscribe from this group, send email to
> symfony-devs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Symfony developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to symfony-devs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
--
If you want to report a vulnerability issue on Symfony, please read the
procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
---
You received this message because you are subscribed to the Google Groups
"Symfony developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to symfony-devs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
