Routix.RPC 2.2
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.
Tags: rpc, remote, procedure, call, network, development, activex, delphi, automation, com, developer, remote procedure call, …
CallbackDisk 1.0
With CallbackDisk you can create and manage virtual disk devices within your application and expose these disks to Windows as if they were real disk devices. The disks become visible to all process in the system. Virtual disk is the one that has a file system on it, but is not physically located on a disk partition. The storage can be actually located in a file residing on a local disk, or in applicaiton resources, or in memory, or somewhere at a remote location. The important part is that this disk is visible to the user (and to other applications) as if it were a formatted hard disk partition.CallbackDisk provides a kernel-mode driver, which calls your application when it needs to perform reading or writing to the disk. And your application can store the actual disk data anywhere it needs: in memory, over the net etc. Virtual disk can be needed, when * the application stores some data internally (in resources or in supplementary files) and it needs to use some library, which can only work with file located within a system-wide file system. The examples include DirectX libraries, Flash player, many third-party components.* the application must hide presence of the disk from the user, while keeping it (the disk) available for some applications* and more ...
Tags: virtual, disk, drive, driver, device, kernel, mode, user, callback, …
Callback File System 1.0
With Callback File System you can create your own file system within your application and expose this file system to Windows as a virtual disk.Callback File System provides a kernel-mode driver, which calls your application when it needs to perform some file system operation, and a user-mode API for use by your application. And your application can expose generic data as a file system to third-party processes.Such approach lets you offer the remotely stored information for system-wide access.
Tags: driver, callback, file, system, mount, user, kernel, mode, …
|