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

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

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. 14 1 Introduction If you wonder which way to choose, here are a few comparisons: Web service 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

.... 16 1.2.14. MQTT ..... 16 1.2.15. Kafka ..... 17 1.2.16. Rest Server ..... 18 1.2.17. SOAP ..... 19 1.2.18. Dropwizard Metrics ..... 19 1.2.19. JDBC ..... 19 1.2.20. ConfigAdmin .... ##### 1.2.17. SOAP The Decanter SOAP collector periodically requests a SOAP service and returns the result (the SOAP Response, or error details if it failed). The decanter-collector-soap feature installs decanter-collector-soap This feature also installs etc/org.apache.karaf.decanter.collector.soap.cfg configuration file where you can setup the URL of the service and the SOAP request to use: # # Decanter SOAP collector

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