Re: [wxperl-users] alternatives to POE

[Foo JH <jhf...@ex...>]

> If your code can be structured as iterators, you don't need threading 
> and it is much simpler to say $thing->work in idle than to try to deal 
> with real asynchronous processing.
>   
Not really. In my client-side app which takes significant time to comms 
with a server, during this time if the client where to simply alt-tab to 
and fro, the wxperl app does not refresh, and it really looks like it hung.

To enable the concept of cooperative multitasking, I'd prob have to 
break up the comms into smaller chunks, and have some form of state 
memory for the poe framework to work. This however is not exactly the 
straightforward style of coding as one would normally do (though this is 
prob an arguable pt).

It seems to me that everyone knows how bad threading is for Perl, and 
rather than openly admit it, we regress (again, another arguable 
position) into cooperative multitasking. IMHO not the right thnig to do.

> --Eric
>