Invocation Styles

DOI Bookmark:

http://doi.ieeecomputersociety.org/10.1109/MIC.2003.1215664

July/August 2003 (vol. 7 no. 4) pp. 83-85

	This Article
	PURCHASE ARTICLE: $19 PDF HTML IEEE Xplore Subscribers
	Share
	Email this Article to a friend
	Bibliographic References
	ASCII Text BibTex RefWorks Procite/RefMan/Endnote
	Add to:
	Digg Furl Spurl Blink Simpy Google Del.icio.us Y!MyWeb
	Search
	Similar Articles Articles by Steve Vinoski

	ASCII Text	x
	Steve Vinoski, "Invocation Styles," IEEE Internet Computing, vol. 7, no. 4, pp. 83-85, July/August, 2003.

	BibTex	x
	@article{ 10.1109/MIC.2003.1215664, author = {Steve Vinoski}, title = {Invocation Styles}, journal ={IEEE Internet Computing}, volume = {7}, number = {4}, issn = {1089-7801}, year = {2003}, pages = {83-85}, doi = {http://doi.ieeecomputersociety.org/10.1109/MIC.2003.1215664}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, }

	RefWorks Procite/RefMan/Endnote	x
	TY - MGZN JO - IEEE Internet Computing TI - Invocation Styles IS - 4 SN - 1089-7801 SP83 EP85 EPD - 83-85 A1 - Steve Vinoski, PY - 2003 VL - 7 JA - IEEE Internet Computing ER -

Steve Vinoski, IONA Technologies

Robust middleware applications require static and dynamic styles of service invocation, which describe the nature of the information that a middleware application requires to properly invoke a given service. To invoke a service, you need to know what to send to it, where to send what you're sending, and what the service will do for you. This article focuses on what to send.

Citation:

Steve Vinoski, "Invocation Styles," IEEE Internet Computing, vol. 7, no. 4, pp. 83-85, July/Aug. 2003, doi:10.1109/MIC.2003.1215664

Peer Review Notice | Give Us Feedback

Usage of this product signifies your acceptance of the Terms of Use.