Introduction to RPC on Windows: Part I
(Page 1 of 6 )
Want to learn how to write distributed applications on the client/server architecture? This article, the first of a series, discusses how to use RPC on Win32 platforms.
Recently I was working on a Smart Card Reader remoting project for which I needed a client-server applications structure to make the client believe that a Smart Card reader is attached to the local machine when the reader will probably be on the other side of the globe. I have been developing application for some time that have similar requirements using RPC as the layer of communication between the client and the server. So I thought it would be a good idea to write an article about a technology that is so powerful and yet so simple.
It’s easy to learn how to use RPC on Win32 platforms, but for better understanding we should first emphasize the basics and then move to advanced topics. So I have divided the whole topic in five articles that you’ll get here on ASP Free. But don’t you worry…I shall provide a working sample application and code with most of them, so you may try it for yourself. For this article you may download the code here.
So let’s get started!
What is this RPC anyway?
Remote Procedure Call (RPC) is a powerful technology that allows you to write distributed applications on the Client/Server architecture. Most of the routine chores of making a connection and communicating between two endpoints are managed by RPC runtime libraries. That means one has more liberty to spend more time on the problem domain (or the problem at hand) rather than the details of the underlying network protocol and communication between client and server.
The title of the article has been chosen carefully because RPC is not a technology by Microsoft; it’s Microsoft’s implementation of the open concept of RPC. This means that if implementations on two platforms exist as per the specification, a client will be able to connect to a server running on another platform. Maybe the server could be written for Linux and the client could be written for Win32.
Next: Meet IDL >>
More .NET Articles
More By Digvijay Chauhan
|
| · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | · | | | | |
|
