atome : ressource (donnée) : REST – orientée service $ ^{2} $ : atome : service (traitement) : RPC (SOAP) ## Service web ## • 2 visions : - Utiliser les technos web pour développer des appliés distribuées Facebook, API Google $ ^{6} $ - IFTTT $ ^{7} $ • Consommer un service web ≠ Créer un service web ## SOAP • AVANT : Simple Object Access Protocol (obsolète) • Evolution de XML-RPC, format XML d'envoi Service (SOA) • Indépendant du langage et de la plateforme • Recommandation du w3c depuis 2003 • SOAP = abus de langage, service web WS-* est plus exact • Specifications WS- $ ^{*8} $ : – spécifications

Node.js, jQuery, AJAX, JSON, ... • Déploiement et configuration Serveur • Webservices : REST vs SOAP • Sécurité : Technologies, prévention des risques courants • (Responsive) Web Design • (Syndication

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you wonder which way to choose, here are a few comparisons: ## 1 Introduction |Web descriptions; and then a client that connects to that web service. The connections are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you are wondering which approach to choose, here are a few comparisons: ## 1 Introduction client that connects to that web service. Connections to the VirtualBox web service are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you wonder which way to choose, here are a few comparisons: ## 1 Introduction |Web descriptions; and then a client that connects to that web service. The connections are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you wonder which way to choose, here are a few comparisons: ## 1 Introduction |Web descriptions; and then a client that connects to that web service. The connections are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you wonder which way to choose, here are a few comparisons: ## 1 Introduction |Web descriptions; and then a client that connects to that web service. The connections are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you wonder which way to choose, here are a few comparisons: ## 1 Introduction |Web descriptions; and then a client that connects to that web service. The connections are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you wonder which way to choose, here are a few comparisons: ## 1 Introduction |Web descriptions; and then a client that connects to that web service. The connections are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the

ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described in a web service API. Technically, the web service is another front-end to this COM API, mapping almost all of it to SOAP clients. If you wonder which way to choose, here are a few comparisons: ## I ntroduction |Web service|COM/XCOM| descriptions; and then a client that connects to that web service. The connections are governed by the SOAP standard, which describes how messages are to be exchanged between a service and its clients; the