|
Remote 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. This technology based on TCP-transport and XML-packets (messages). 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.
Routix.RPC: http://www.routix.net/rpc/files/Routix.RPC.zip
Java Distributed Refreshable Objects: http://www.fusionsoft-online.com/refreshableobject.php
Distributed Refreshable Objects (DRO) is a software library for Java developers enhancing inter-object communication in local as well as distributed environments, which can be considered as more effective and flexible alternative to CORBA and other distributed-object infrastructures.
DRO helps solve the following problems:
Tuning efficiency of distributed application code
Maintaining the viability of applications in the face of change
The obsolescence of cached data
Central server bottleneck
The key features are:
Effective network data interchange
Caching resource-intensive calculated properties without stale data
Change tracking for object properties
Informative network packets debugging
No any messaging server needed
Wide possibility to optimize network traffic
А bunch of iterator elements is transmitted at a time
A refreshable object provides change tracking for object properties, proper as well as calculated from other objects’ properties, and it provides caching resource-intensive calculated properties without stale data. All this is done transparently for programmers.
The distributed object intercommunication layer provides much more effective network data interchange since several remote calls are collected and sent as one package. This functionality is supported in distributed environment with no any messaging server, peer-to-peer connections are organized instead, which gives very high scalability.
All distributed objects in DRO are cached on client side, so repeated use of object properties does not result in network exchange. However, when a server object is modified, all its cached client copies become updated; no stale data are possible.
In sum, DRO gives means to create distributed as well as local applications with high flexibility and efficiency. No code structure modification is necessary to add resource-intensive calculated property caching, and to migrate an application into distributed environment efficiently. |