OperationContract(IsOneWay=True) == HTTP/1.1 202 Accepted

To those whom have attended Indigo Ascend and have asked me via emails: What acutally happens in the plumbings of the IsOneWay part of a Indigo Duplex Contract 

HTTP/1.1 202 Accepted is the answer. This is the explicit return.

HTTP/1.1 100 Continue

HTTP/1.1 202 Accepted
Date: Fri, 15 Jul 2005 08:56:07 GMT
Server: Microsoft-IIS/6.0
MicrosoftOfficeWebServer: 5.0_Pub
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50215
Cache-Control: private
Content-Length: 0

This, of course, only applies to the HTTP Bindings.

"The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.

The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent`s connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request`s current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled."

No manipulation of threads and callbacks and delegates required.