r, as well as an asynchronous interface to signal the need to refresh the Web interface. 3.2.4 Web 2.0 Technologies in the WIMS 2.0 SDP The WIMS 2.0 platform eases the technology transition from the Telco technology domain toward the pure Internet technology domain aiming at facilitating the dialogue between a telecom world and the Web 2.0, from the operator perspective. Figure 3.3 depicts a summarized view of the entire Web technologies consid- ered representing the domain of scope of each one of them. Before describing each of the different groups identified in Figure 3.3 and the relationship with the implementation of the WIMS 2.0 service platform, it is important to stress the principles that organize this technology map: 1. Technologies have been located following the client-server paradigm that governs the Web world. Within the server and the client sides, the different groups comprise technologies for the implementation of similar functional- ities which might be complementary, for example, the AJAX set of technolo- gies, or represent an alternate choice to provide the same functionality, for example, JavaScript and ActionScript. 2. HTTP protocol is the base for all interactions between remote elements, independently of the nature of those elements. These interactions are retrieval and manipulation of Web page contents and the usage of Web-ready APIs. 3. As a featured concept in Web 2.0, remote APIs are of paramount importance to support the mash-up of functionality within a given service. In the map, there are two variants of the usage of Web-ready APIs: a. Client-server scenario, where a browser directly invokes the API by send- ing HTTP request to a remote server. Service Delivery Platforms Web client Server side API exposure Web pages Web page server Development Paradigms Structure and Contents Server HTML, XHTML FRAMEWORKS and Protocols HTML, XML, XHTML, DOM CSS, Scripts, etc. Ruby on Rails presentation logic, ColdFusion Method Presentation WSPs, ASPs, PHP, etc. Django oriented (RPC): XML-RPC, SOAP, I