{'fraction_non_alphanumeric': 0.02119071644803229, 'fraction_numerical': 0.0030272452068617556, 'mean_word_length': 5.08282208588957, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Support of an Actor Environment on Distributed Architectures

Distributed Programming is not easy and parallel objects languages (for instance Actor languages) are a well suited way to facilitate the programming of Distributed Architectures. Our research team works on the design and the implementation of Parallel Object Languages for Distributed Architectures (multicomputer or Workstation network). We promote a unique structuring entity for the distributed programming: We call it Cac (Communicating Active Component). A Cac is an entity which includes a local context, a mailbox and an activity running a behavioral function. A concurrent application may be defined as a set of Cac/s communicating by message sending. Before execution, the code of behavioral functions is distributed on several nodes. During execution, the Cac/s of application run concurrently on the network nodes. Actor Languages may be implemented with Cac/s. So the execution of program with Actors produces a real parallelism and a natural distribution of actors over the network. A prototype for the Actor model was developed on Cac run-time. This is a specialization of the Cac run-time for the actor model. The model has to suggest a distribution of actors and script codes on the different nodes of the target machine. We describe Cac implementation on a network of SPARCstations by using SunOS 4.1 and especially the lightweight processes (Cac activity) and the sockets. The Cac environment is easily realizable on a modern distributed operating system. Another implementation is made on a Transputer-based multicomputer (Parsytec Multicluster II) with the Helios operating system. We plan a new development with Solaris 2 and especially the multithread functionalities. Threads and LWP/s of Solaris 2 are more efficient and interesting because they are managed by the kernel; therefore they can execute independent system calls. The threads of Solaris 2.0 take advantage of multiprocessor hardware.