{'fraction_non_alphanumeric': 0.016564952048823016, 'fraction_numerical': 0.0017436791630340018, 'mean_word_length': 5.41340782122905, '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}}
Connection management in a Lakes environment

Lakes is an architecture for collaborative working developed to support a wide range of collaborative applications of the `same time/different place' variety across different platforms and communication media. When applications wish to share data in such an environment, connections must be established and channels created to provide the necessary communication links. As new nodes join or leave the conference, new connections must be made or broken. If an application is using several distinct channels for different types of data, the management and control of these channels can be a complex task. This paper presents an overview of the Lakes architecture and focuses on two particular features which have been designed to reduce the burden of connection and channel management on the application programmer: (1) the ability of one particular Lakes application, the call manager, to provide flexible connection management on behalf of other applications; and (2) the facility to request that channels are automatically created and destroyed as applications are shared into or unshared from calls.