{'fraction_non_alphanumeric': 0.026357827476038338, 'fraction_numerical': 0.003194888178913738, 'mean_word_length': 5.328282828282828, '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}}
An Infrastructure for Secure Interoperability of Agents

Abstract : Introduction Building distributed applications is difficult. Therefore, it is hardly surprising that in spite of all the hoopla surrounding the Internet and distributed computing, truly distributed applications are few and far between. The problem seems to be with the tools available to developers of distributed applications. For example, the most widely used mechanism for distributed computation is the remote procedure call (RPC), the first implementation of which dates back to the early 1980s. Typically, a remote procedure call is executed on a server on behalf of a client (the so-called client-server model). It is hardly surprising therefore that most distributed applications today are exclusively based on the client server architecture. A lot can be (and has been) accomplished with this architecture, as exemplified by the World Wide Web and HTTP, a protocol that implements RPC. However, the client-server model has a number of limitations. There are problems of fault tolerance, load balancing, survivability, dynamic reconfiguration, rollover recovery, and distribution of control. Attempts in the past to break through this bottleneck have had only limited success.