Outils pour utilisateurs
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édentes Révision précédente Prochaine révision | Révision précédente Dernière révision Les deux révisions suivantes | ||
|
cours:service_oriented_computing_and_web_services_2018_2019 [2019/04/24 12:52] tigli [Session 3 : Windows Communication Fundation (WCF) and ABC model] |
cours:service_oriented_computing_and_web_services_2018_2019 [2019/04/24 12:57] tigli [Session 3 : Windows Communication Fundation (WCF) and ABC model] |
||
|---|---|---|---|
| Ligne 165: | Ligne 165: | ||
| === Advanced Lecture on ABC and WCF === | === Advanced Lecture on ABC and WCF === | ||
| - | == Synchronous and Asynchronous Operations in WCF services == *Types of Asynchronous Operations | + | == 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. | + | |
| - | + | ||
| - | The independence of the service contract from either the service or client implementation enables the following forms of asynchronous execution in WCF applications: | + | |
| - | + | ||
| - | Types of Asynchronous Operations | + | |
| 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. | 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. | ||
| Ligne 185: | Ligne 177: | ||
| * Services can implement a request/response operation asynchronously using a synchronous message exchange. | * Services can implement a request/response operation asynchronously using a synchronous message exchange. | ||
| - | Message exchanges can be one-way, regardless of the implementation of the client or service. | + | * Message exchanges can be one-way, regardless of the implementation of the client or service. |
| - | * Clients can invoke request/response operations asynchronously using a synchronous message exchange. | + | |
| - | + | ||
| - | Services can implement a request/response operation asynchronously using a synchronous message exchange. | + | |
| - | + | ||
| - | Message exchanges can be one-way, regardless of the implementation of the client or service. | + | |
| - | [[https://docs.microsoft.com/fr-fr/dotnet/framework/wcf/synchronous-and-asynchronous-operations|Find here details on the different kinds ]] | + | [[https://docs.microsoft.com/fr-fr/dotnet/framework/wcf/synchronous-and-asynchronous-operations|Find here details on the different types of Asynchronous Operations in WCF services]] |
| == System.ServiceModel Namespace == | == System.ServiceModel Namespace == | ||
| Ligne 200: | Ligne 186: | ||
| [[https://docs.microsoft.com/fr-fr/dotnet/api/system.servicemodel?view=netframework-4.8|Find the System.ServiceModel Namespace description here and some complete source code instead of App.config configurations]] | [[https://docs.microsoft.com/fr-fr/dotnet/api/system.servicemodel?view=netframework-4.8|Find the System.ServiceModel Namespace description here and some complete source code instead of App.config configurations]] | ||
| - | == netTcpBinding == | + | == 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. | 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. | ||
cours/service_oriented_computing_and_web_services_2018_2019.txt · Dernière modification: 2019/05/12 16:58 par tigli
Outils de la page
Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : CC Attribution-Noncommercial-Share Alike 4.0 International
