{'fraction_non_alphanumeric': 0.022222222222222223, 'fraction_numerical': 0.0, 'mean_word_length': 5.4, '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}}
Client-side service composition using generic service representative

Traditionally, composition of web services is performed at the server-side. This requires transferring client data among collaborating web services, which may cause data privacy violation, security breaches, or network traffic overloading. In this context, we introduce the concept of "task service" which is a web service that can process the client data locally at the client-side using a generic software agent that we call "service representative". The proposed task service and service representative allow us to present a new concept called "client-side service composition", where collaborating web services employ the service representative to provide a composite task service at the client side. Therefore the client is not required to reveal its resources to service providers and hence its privacy and security are maintained. Moreover, large client data are processed locally that results in less network traffic. We have developed a prototype system for the proposed extended SOA model. Finally, we will discuss the advantages of the proposed approach over traditional server-side approaches using a case study in healthcare domain.