kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/p5-Mojo-IOLoop-ForkCall/distinfo

7 lines
452 B
Text
Raw Normal View History

p5-Mojo-IOLoop-ForkCall: update to 0.20 0.20 2018-09-14 - Deprecate in favor of Mojo::IOLoop::Subprocess - Protect against removal of delay helper in Mojolicious 7.90
2018-10-11 22:26:12 +02:00
$NetBSD: distinfo,v 1.9 2018/10/11 20:26:12 wiedi Exp $
Import p5-Mojo-IOLoop-ForkCall-0.14 as devel/p5-Mojo-IOLoop-ForkCall Asynchronous programming can be benefitial for performance, however not all functions are written for nonblocking interaction and external processes almost never are. By forking the blocking call into a new process, the main thread may continue to run non-blocking, while the blocking call evaluates. Mojo::IOLoop::ForkCall manages the forking and will emit an event (or execute a callback) when the forked process completes. Return values are serialized and sent from the child to the parent via an appropriate pipe for your platform.
2014-08-30 12:53:51 +02:00
p5-Mojo-IOLoop-ForkCall: update to 0.20 0.20 2018-09-14 - Deprecate in favor of Mojo::IOLoop::Subprocess - Protect against removal of delay helper in Mojolicious 7.90
2018-10-11 22:26:12 +02:00
SHA1 (Mojo-IOLoop-ForkCall-0.20.tar.gz) = 980e725c0b39ae1b221965dff8dbba20b1507426
RMD160 (Mojo-IOLoop-ForkCall-0.20.tar.gz) = 69b3271dbe9c80e0fc36a665004caac2371e1b8e
SHA512 (Mojo-IOLoop-ForkCall-0.20.tar.gz) = 44419735e1b8d74592d9eb0f50ea6fa2ff604480842d13e3e3d25317dc31ae151fbd9daae1f3c8256c85a497e05358290888f4d2fdac85fad396672b02b732ca
Size (Mojo-IOLoop-ForkCall-0.20.tar.gz) = 10605 bytes
Reference in a new issue Copy permalink