Hello Deepsmj,
In general terms, the phrase "distinct executions" simply refers to
running (or executing) a program one or more times. For example, if
you use the Unix command
ls
one or more times, each time counts as a "distinct execution". Note
that the results of a distinct execution may be the same or vary based
upon the initial conditions. Some languages such as Ada requires
consistency in distinct execution - for reference:
http://www.adaic.org/standards/95aarm/html/AA-10-2-1.html
from the Annotated Ada Reference Manual; section 10. A distinct
execution in this case refers to the execution of a package that can
be included in one or more main programs. [note that Ada provides
direct support for multiple tasks and distributed application
development]
Applying the phrase "distinct executions" to a distributed system is
not so clear. For example,
http://www.cs.wustl.edu/~schmidt/PDF/OORTDCSpaper.pdf
is a report describing the IKE-2 distributed object middleware, uses
the phrase "distinct executions" on page 6. Note in this case that an
"execution" does not directly map into a process, main program, nor
session. An execution is some type of hybrid that spans a set of
computing assets and may share resources (e.g., a process) with other
executions.
There are other references; a focused search on this was done using
the phrases
definition "distinct executions" "distributed system"
or
"distinct executions" distributed systems
will provide a few more references for comparison. Please note that
the definitions are not so clear in these other cases.
If you have a specific application area or context that this should be
applied - please provide that in a clarification request so I can
pursue this more fully.
--Maniac |
