loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Web Services Notifications
March/April 2004 (vol. 8 no. 2)
pp. 86-90
ASCII Text
x 
 
Steve Vinoski, "Web Services Notifications," IEEE Internet Computing, vol. 8, no. 2, pp. 86-90, March/April, 2004.
 
 
BibTex
x
 
@article{ 10.1109/MIC.2004.1273491,
author = {Steve Vinoski},
title = {Web Services Notifications},
journal ={IEEE Internet Computing},
volume = {8},
number = {2},
issn = {1089-7801},
year = {2004},
pages = {86-90},
doi = {http://doi.ieeecomputersociety.org/10.1109/MIC.2004.1273491},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Internet Computing
TI - Web Services Notifications
IS - 2
SN - 1089-7801
SP86
EP90
EPD - 86-90
A1 - Steve Vinoski,
PY - 2004
KW - Web services
KW - wsdl
KW - ws-events
KW - asynchronous
KW - push
VL - 8
JA - IEEE Internet Computing
ER -
 
Steve Vinoski, IONA Technologies
As Web services have matured, they?ve also acquired the need for asynchronous push capabilities. Early Web services were seemingly all remote procedure call (RPC)-oriented. In an RPC system, the receiver normally 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.
Index Terms:
Web services, wsdl, ws-events, asynchronous, push
Citation:
Steve Vinoski, "Web Services Notifications," IEEE Internet Computing, vol. 8, no. 2, pp. 86-90, Mar./Apr. 2004, doi:10.1109/MIC.2004.1273491
Usage of this product signifies your acceptance of the Terms of Use.