| Name : perl-Process
| |
| Version : 0.300.0
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : lp155.1.1
| Date : 2024-07-28 00:13:07
|
| Group : Unspecified
| Source RPM : perl-Process-0.300.0-lp155.1.1.src.rpm
|
| Size : 0.11 MB
| |
| Packager : https://www_suse_com/
| |
| Summary : Objects that represent generic computational processes
|
Description :
There are a great number of situations in which you may want to model a
computational process as an object.
An implementation of this sort of object generally looks like the following
when somebody uses it.
my $object = MyProcessThingy->new( ... );
my $rv = $object->run;
if ( $rv ) {
print \"Thingy ran ok\";
} else {
print \"Failed to run thingy\";
}
The \'Process\' family of modules are intended to be used as base and role
classes for these types of objects. They are used to help identify process
objects, and enforce a common API on these objects.
The primary intent is to provide a common base for objects that will be
able to be used with various distributed processing systems, without itself
actually implementing any form of distributed system.
The scope of uses for Process includes solutions to address the following
scenarios.
* A single CPU on a single host
* Multiple CPUs on a single host
* Multiple hosts on a single network
* Hosts distributed across the internet
* Any processing resource accessible via any mechanism
To put it another way, this family of classes is intended to addresses the
separation of concerns between the processing of something, and the results
of something.
The actual ways in which the processes are run, and the handling of the
results of the process are outside the scope of these classes.
The \'Process\' class itself is the root of all of these classes. In fact, it
is so abstract that it contains no functionality at all, and serves
primarily to indicate that an object obeys the general rules of a \'Process\'
class.
Most of the basic \'Process\' modules are similar. They define how your
object should behave (an API for a particular concept) without dictating a
particular implementation.
However, by using them, you are confirming to some processing system that
your objects will obey particular rules, and thus can interact sanely with
any processing system that follows the API.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/15.5/noarch |
