Yes, from your description you seem to be trying to shoehorn a sequential program into an event loop. AnyEvent (or POE, or IO::Async, or whatever) is not a hammer for every nail, it is not always appropriate, but I'm not certain I'd recommend threads either, perhaps a combination of fork and some form of IPC (using one of the fine modules on CPAN, such as Parallel::ForkManager) might be better. It would definitely make good use of your pre-emptive, multi-tasking operating system. | [reply] |
I think I need to re-think my design...
If you are able to post a description of the application, I'd be more than willing to offer suggestions on how you might tackle it with threads.
Maybe we could even get one of the events guys to knock up a solution also and then compare results.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
I think I will now revert to doing more actual development on the system after all the input, to find out where the real challenges lie.
...before I begin to post gory details which might turn out as being sideshows... ;)
Thanks everyone!
| [reply] |
..before I begin to post gory details which might turn out as being sideshows..
Fair enough.
I originally started out writing a short, pithy reply here, but it turned into another long-winded "opinion piece". So, in respect of your wish for no more sideshows, I'm posting it as a meditation instead.
| [reply] |