{'fraction_non_alphanumeric': 0.020287958115183247, 'fraction_numerical': 0.0013089005235602095, 'mean_word_length': 5.165322580645161, '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}}
A DEPLOYMENT-READY SOLUTION FOR ADDING QUALITY-OF-SERVICE FEATURES TO WEB SERVICES

Web Services is a recent technology that enables an application to interact with a remote application over the Internet and use its functionality. The novelty of the Web Services technology is that it allows heterogeneous applications to interact with each other regardless of their development and operational platforms. Quality-of-Service (QoS) features such as security, reliability and manageability are vital to enterprise-class applications. Several solutions exist to achieve QoS in Web Services, one of which is Web Service intermediaries. The advantage of Web service intermediaries over other solutions is that it takes most of the load of implementing QoS in Web Services off their developers. However, current implementations of the Web Service intermediary solution have some undesirable constraints, which include: 1) the requirement of recoding to enable a Web Service application to interact with the intermediary, and 2) the need for a central server in the intermediary architecture. Recoding a Web service application is a time and effort consuming task. A central server is not suitable when centralization of control in a single authority is undesirable. We present a Web Service intermediary based on the peer-topeer architecture which does not suffer from these problems. The solution does not require recoding of a Web Service application. Due to the peer-to-peer architecture, it also does not require a central server.