Re: Performance of many concurrent delay() calls

["Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>]

On 11/09/2016 08:50 AM, Olivier Henley wrote:
>
> Right now I am doing the following inside the On_Connect handler
>
> loop
>   if Main_Window.Connection_Data = null then
>     exit;
>   end if;

exit when Main_Window.Connection_Data = null;

>   App_Central.Process_Message (App_Data);
>
>   delay 1.0;
> end loop;
>
> Is it fine or the usage of a task is strongly recommended and for what reasons?

I don't know. IIUC, Gnoga creates a task to call the on-connect handler, and 
you're keeping that task busy in the handler for the life of the connection. I 
don't know what the effect of that on the Gnoga internals might be. If it works 
OK for lots of connections, then it's probably OK. Botton would know for sure. 
Personally, I'd rather not tie up a task from a library without knowing more 
about what the consequences are.

-- 
Jeff Carter
"I've seen projects fail miserably for blindly
applying the Agile catechism: we're Agile, we
don't need to stop and think, we just go ahead
and code!"
Bertrand Meyer
150