Simple Object Access Protocol is a XML based protocol. It enables applications to communicate with each other.
The main purpose of using SOAP is to enable communication between two independent applications using different technology, hosted on different environment.
HTTPS, "Hyper Text Transfer Protocol" with Secure Sockets Layer (SSL)
Using SSL in your application requires special authorization from a recognized certificate authority. This authorization comes in the form of a server certificate, which you install in IIS to identify your server. The certificate authority licenses server certificates (for a fee) and acts as a clearinghouse to verify your server’s identity over the Internet.
When a user’s browser begins secure communications, it requests the server certificate and checks it against a list of trusted sites provided by the certificate authority. If the server certificate does not match one of the sites already authorized by the user, or if the server certificate does not match the Web address for which it was registered, or if there are any other problems with the server certificate, the browser displays a warning.
In this way, the certificate authority not only provides encryption for secure data transmission, but it also provides assurance to users that your Web site is authentic.
The Secure Sockets Layer (SSL) is the standard means of ensuring that data sent over the Internet can’t be read by others. When a user requests a secure Web page, the server generates an encryption key for the user’s session and then encrypts the page’s data before sending a response. On the client side, the browser uses that same encryption key to decrypt the requested Web page and to encrypt new requests sent from that page.
This is the techniques used by WCF to bind client requests to service instances, using these technique service instance handles and decides how an which client request will be handled by which service.
In a Percall instance mode, a new service object is created for each call.
- Less memory consumption
- Service instances are freed
- Concurrency is not an issue
- PerCall services increase overall throughput
- State not maintained between calls
- Transport session
- Reliable sessions
- Secure sessions
- Application sessions
In a single instancing mode, a single service object is created for all calls coming from all the clients and sessions. This type of WCF service is also called as singleton service. The following are the advantages and Disadvantages of Single instance mode of Singleton Service.
State maintained by service instance
Potentially greater memory consumption
Its, 10 minutes by default, for Application Session.
In a Single concurrency mode only one request is processed at a time by the same service instance. A lock is acquired while a request is processed by a service instance, other requests are queued if they try to same instance of the service. Once the request is processed and lock is released then the next request in the queue can be processed by the service instance.
Yes, The concurrency mode of a WCF service is Single by default.
- TransactionFlowOption.NotAllowed: No transaction will be allowed even if any client attempts to call the service in transaction.This is a default option.
- TransactionFlowOption.Allowed: Client may or may not call service in a transaction. It’s not compulsory for the client to call the service in a transaction.
- TransactionFlowOption.Mandatory: Client must call the WCF service in a transaction. If the WCF service is called without transaction, ‘FaultException’ will be raised.