Client-Server Generic XML, API client RSS, Atom 1.0, JSON, Serialized PHP Browser: IE, Mozilla, Opera, Safari HTTP (for API usage) Figure 3.3 The WIMS 2.0 SDP technology map. Server-server scenario, where a server is the actor invoking the APIs provided by another server. The invoking server is acting as a Web client as far as the usage of API is concerned. Normally this scenario is used to prevent the Web browser to realize this kind of actions, and thus, all the service logic to handle the remote API is managed by the server. Once principles are explained, technologies are grouped as follows: Client side: The client side comprises all technologies that are typically used by Web browsers. The following groups and subgroups are considered. Web pages technologies related to presentation and processing of Web pages. There are three technological levels: Structure, comprising all technologies to support information, both contents and semantics, and the Web page structure. HTML, XHTML, XML, and DOM are technologies within this level. Presentation, comprising technologies to control how the information is presented. CSS is the most representative one in this level. Behavior, which gathers all technologies used to implement the logic that control local actions and dynamic behavior of the Web page. This dynamic activity can result in modifications over the presentation and structure Moving the SDP to the Cloud levels. VisualBasic Script, Javascript, ActionScript, ActiveX are some of the ones considered. Technologies for Web API clients in the Web browser include the technologies in charge of the process, form and send HTTP request toward remote APIs and to receive and interpret responses according to specific data formats. Since these actions can be considered as dynamic behavior of the Web page, lan- guages which rule this level are the same than those utilized in the Web page behavior level. Browsers are those alternative options as client platforms, for example, Internet Explorer, Mozilla Firefox, Opera, Safari, and 