Process
From Friend2Friend Wiki
Processes are constructs designed to complement the hierarchical structure of threads and servicereqs. In contrast to threads, they are addressable from outside their hierarchy. Each process has a URI which must be unique of all processes running at that particular node. They a set of users (c.f. subscribers) and their own datastore, which is inaccessible from anywhere else.
Contents |
Child Threads
Processes have a set of child threads, which have the process as their parent but are otherwise the same as other threads running at that soft node. By default, processes terminate once all their child threads have terminated.
Receiver Script
Processes receive data which is passed back in messages from their child threads. They respond to this depends upon their <f2f:receiver-script> element.
Process Users
The creator of a process is its first user, who may choose to allow other users to connect to a process, which gives them access to either push or pull data feeds. For example, they might choose to be informed whenever a process' datastore was modified, if it received a particular type of element.
