cours:service_oriented_computing_and_web_services_2018_2019
Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédenteDernière révisionLes deux révisions suivantes | ||
cours:service_oriented_computing_and_web_services_2018_2019 [2019/04/24 06:03] – [Session 3 : Windows Communication Fundation (WCF) and ABC model] tigli | cours:service_oriented_computing_and_web_services_2018_2019 [2019/04/24 10:57] – [Session 3 : Windows Communication Fundation (WCF) and ABC model] tigli | ||
---|---|---|---|
Ligne 163: | Ligne 163: | ||
/* {{ : | /* {{ : | ||
- | === Lecture | + | === Advanced |
- | ||| | + | |
- | Windows Communication Foundation (WCF) provides a rich infrastructure for exporting, publishing, retrieving, and importing service metadata. WCF services use metadata to describe how to interact with the service' | + | |
- | === Lecture 3 : MEX and Web Services : WSDL === | + | == Types of Asynchronous Operations in WCF services |
- | ||| | + | All service contracts in WCF, no matter the parameters types and return values, use WCF attributes to specify a particular message exchange pattern between client and service. WCF automatically routes inbound and outbound messages to the appropriate service operation or running client code. |
+ | The client possesses only the service contract, which specifies the message exchange pattern for a particular operation. Clients can offer the developer any programming model they choose, so long as the underlying message exchange pattern is observed. So, too, can services implement operations in any manner, so long as the specified message pattern is observed. | ||
- | * {{:cours: | + | The independence of the service contract from either the service or client implementation enables the following forms of asynchronous execution in WCF applications: |
+ | * Clients can invoke request/ | ||
- | /* * {{: | + | * Services can implement a request/response operation asynchronously using a synchronous message exchange. |
- | */ | + | |
- | === Advanced Lecture | + | * Message exchanges can be one-way, regardless of the implementation of the client or service. |
+ | |||
+ | [[https:// | ||
+ | |||
+ | == System.ServiceModel Namespace | ||
+ | App.config is an XML file to set a list of parameters required to instanciate some classes of the System.ServiceModel Namespace. | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | == non-http binding for non web based services : netTcpBinding == | ||
+ | |||
+ | ABC Model is not only dedicated to Web Service but can use non over http binding like direct TCP/IP protocol. One of the standard Binding for that is netTcpBinding. | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | Here you can see that the App.config file is only an other way to defined different parameters | ||
== WCF Hosting == | == WCF Hosting == | ||
Ligne 197: | Ligne 211: | ||
Here find most of the possible extensions : [[https:// | Here find most of the possible extensions : [[https:// | ||
- | https:// | ||
+ | |||
+ | ===== Session 4 : MEX and Web Services and WSDL ===== | ||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | ||| | ||
+ | |||
+ | |||
+ | === Lecture 1 : ABC Model and MEX Contract === | ||
+ | ||| | ||
+ | Windows Communication Foundation (WCF) provides a rich infrastructure for exporting, publishing, retrieving, and importing service metadata. WCF services use metadata to describe how to interact with the service' | ||
+ | |||
+ | === Lecture 2 : WSDL and Web Services === | ||
+ | ||| | ||
+ | {{: | ||
+ | |||
+ | |||
+ | /* * {{: | ||
+ | */ | ||
+ | |||
+ | === TIPS === | ||
+ | |||
+ | [[https:// | ||
===== Advanced Session 1 : Event Based Communication and Architecture with web services | ===== Advanced Session 1 : Event Based Communication and Architecture with web services | ||
cours/service_oriented_computing_and_web_services_2018_2019.txt · Dernière modification : 2019/05/12 14:58 de tigli