RPC Under Fire

DOI Bookmark:

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

September/October 2005 (vol. 9 no. 5) pp. 93-95

	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, "RPC Under Fire," IEEE Internet Computing, vol. 9, no. 5, pp. 93-95, September/October, 2005.

	BibTex	x
	@article{ 10.1109/MIC.2005.108, author = {Steve Vinoski}, title = {RPC Under Fire}, journal ={IEEE Internet Computing}, volume = {9}, number = {5}, issn = {1089-7801}, year = {2005}, pages = {93-95}, doi = {http://doi.ieeecomputersociety.org/10.1109/MIC.2005.108}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, }

	RefWorks Procite/RefMan/Endnote	x
	TY - MGZN JO - IEEE Internet Computing TI - RPC Under Fire IS - 5 SN - 1089-7801 SP93 EP95 EPD - 93-95 A1 - Steve Vinoski, PY - 2005 KW - middleware KW - distributed systems KW - remote procedure calls KW - RPC KW - C-omega KW - JAX-RPC KW - REST VL - 9 JA - IEEE Internet Computing ER -

Steve Vinoski, IONA Technologies

Despite the fact that many successful distributed systems have been built using remote procedure calls, we've also known for a while that RPC is imperfect, even fundamentally flawed. Lately, however, it seems to be taking even more heat than usual, mainly because of continuing advances in Web services and XML-based messaging.

Index Terms:

middleware, distributed systems, remote procedure calls, RPC, C-omega, JAX-RPC, REST

Citation:

Steve Vinoski, "RPC Under Fire," IEEE Internet Computing, vol. 9, no. 5, pp. 93-95, Sep./Oct. 2005, doi:10.1109/MIC.2005.108

Peer Review Notice | Give Us Feedback

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