| Name : perl-POE-Component-Generic
| |
| Version : 0.140.300
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : lp155.1.1
| Date : 2024-03-12 18:23:39
|
| Group : Unspecified
| Source RPM : perl-POE-Component-Generic-0.140.300-lp155.1.1.src.rpm
|
| Size : 0.11 MB
| |
| Packager : https://www_suse_com/
| |
| Summary : Generic non-blocking POE interface to any OO-module
|
Description :
POE::Component::Generic is a POE component that provides a non-blocking
wrapper around any object. This allows you to build a POE component from
existing code with minimal effort.
The following documentation is a tad opaque and complicated. This is
unavoidable; the problem POE::Component::Generic solves is complicated.
POE::Component::Generic works by forking a child process with
POE::Wheel::Run and creating the blocking object in the child process.
Method calls on the object are then serialised and sent to the child
process to be handled by the object there. The returned value is serialised
and sent to the parent process, where it is posted back to the caller as a
POE event.
Communication is done via the child\'s \'STDIN\' and \'STDOUT\'. This means that
all method arguments and return values must survive serialisation. If you
need to pass coderefs or other data that can\'t be serialised, use callbacks
or postbacks.
If you want to have multiple objects within a single child process, you
will have to create factories that create the objects.
Method calls are wrapped in \'eval\' in the child process so that errors may
be propagated back to your session. See OUTPUT.
Output to \'STDERR\' in the child, that is from your object, is shown only if
debug or verbose is set. \'STDOUT\' in the child, that is from your object,
is redirected to STDERR and will be shown in the same circomstances.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/15.5/noarch |
