{'fraction_non_alphanumeric': 0.0215633423180593, 'fraction_numerical': 0.0, 'mean_word_length': 5.575221238938053, '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}}
Asynchronously Rendering Interoperable Remote Portlets

Under current synchronous portal rendering mechanism, a user has to wait until all the portlets are ready for the next interaction. In the case of consuming remote portlets with Web services for remote portlets (WSRP) specification, the situation can be worse. To improve user experiences, an asynchronous mechanism is proposed in this paper leveraging popular Ajax technology. We also discussed several issues such as URL rewriting, cross-portlet interaction, security, etc. that have to be considered while applying asynchronous mechanism, and built up a prototype to prove that using Ajax in rendering remote portlets while providing cross-portlet interaction capability is feasible.