Skip to Main Content
As Web services have matured, they've also acquired the need for asynchronous push capabilities. Early Web services, such as those for getting traffic or weather reports or for performing currency exchange-rate calculations, were seemingly all remote procedure calls-oriented. In an RPC system, the receiver typically performs the requested service and sends a response back to the caller over the same connection on which the request arrived, which means the details required by the service for sending a reply are implicit in the RPC network connection. Unfortunately, these kinds of implied communication details are wholly inadequate for asynchronous push Web services.