cxbrooks
commented
19 years ago In April, Dominique Ragot from Thales submitted a Distributed Process Network domain.
--start-- The PtolemyII DPN 1.0 consists of a Java package that introduces a new domain in PtolemyII named "Distributed Process Network" (DPN). The DPN domain supports the execution in a distributed context of the Kahn Process Network (PN) domain of PtolemyII. For more information on the PN domain, refer to the PtolemyII documentation.
The main difference between the PN and the DPN domain is the use of a distributed fifo that enables the transfer of tokens between actors located on different hosts.
A distributed fifo is composed of two fifo-channels linked together. The first one is a passive fifo-channel that contains a local fifo queue binded in a naming service (see section 2.1). The second one is an active fifo-channel that contains:
- one local fifo queue
- one proxy of the remote passive fifo-channel, and
- one transfer token thread.
The transfer token thread manages the unidirectionnal transfer of
tokens between the local and the remote fifo-channel. It either
produces or consumes tokens, depending on the
of the active fifo-channel: a) if = "prod", the active fifo-channel transmit tokens from the local fifo-channel to the remote one. b) if = "cons", the active fifo-channel transmit tokens from the remote fifo-channel to the local one. The distributed fifo has been designed to run similarly whichever middleware is chosen. Two middlewares are supported in the DPN API v1.0: RMI (over IIOP or JRMP) and CORBA. --end--
The changes are rather hefty and are based on Ptolemy II 2.0, so rather than update the tree, I checked the jar file into $PTII/ptolemy/apps/dpn.
Note: the issue was created automatically with bugzilla2github tool
Original bug ID: BZ#6 From: @cxbrooks Reported version: 4.1