Routix.RPC 3.0
emote procedure call (RPC) is a technology that allows a computer program to cause a subroutine or procedure to execute in another address space (commonly on another computer on a shared network) without the programmer explicitly coding the details for this remote interaction. That is, the programmer would write essentially the same code whether the subroutine is local to the executing program, or remote. When the software in question is written using object-oriented principles, RPC may be referred to as remote invocation or remote method invocation. All communications is transparent for developer. You need write code like for local object. You don't see differences between local and remote objects.
Routix software develop own RPC technology known as Routix.RPC. Our technology differs from other implementations in the high speed of calls, ease of use, support of callback-objects.
Routix.RPC use strong encryption and intellectual compression of network communications between client and server. If you purchased Routix.RPC with source code - you can simply extend communication protocol by adding your custom data to the packets because Routix.RPC use XML-packets as communication protocol. Routix.RPC can be used in distributed N-tier applications, service-console applications, remote management software.
Requirements
Changes: 3.0
- Server and Client objects placed in one ActiveX library (RoutixRPCCOM.dll) instead of separated libraries;
- Transport protocol now is binary instead of XML. Hence we have increased calls speed (10x times) and decreased network traffic more than twice;
- More stable;
