|
Download
Online App Box . DISTRIBUTED APPLICATION, APPLICATION DISTRIBUTED |
|
|
|
|
|
java distributed objects
application integration
Distributed VPN
feed reader application
distributed teams
java distributed systems
Distributed Workgroups
live help application
-------------------------
|
|
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.
Java Distributed Refreshable Objects: http://www.fusionsoft-online.com/refreshableobject.php |
|
Entry Service (ES) 3.1 is a software library for Java developers. It provides centralized access to distributed data though a single hierarchy of typed objects (entries). Entries can be stored in data sources of different types (XML files, RDBMS, etc.). Every data source is to be overbuilt with one entry service; services group together into one distributed hierarchy. Every service publishes its own part of a global entry (object) tree. The whole entry tree is accessible through any service running, through one program interface, in spite of where and how the objects are stored in fact. All the services provide the same view of data transparently.
Entries have stable and unique string identifier to refer from anywhere; the identifier reveals entry nesting structure. Entry nesting and service hierarchy are independent one from another, so entries can be moved into another service without changing their identifiers. ES-Path (XQuery/XPath-like language) exists to query the entry tree.
Distributed Refreshable Objects underlies this library, which adds more flexibility and efficiency to ES: a bunch of remote calls are collected and sent as one package through network; all remote entries are cached on client side with no stale data possible; subscription on entry changes is possible. All this is done with no any messaging server (peer-to-peer communication takes place), which gives very high scalability of the entry tree and possibility to use it in global scope.
The key features are:
- Single view of typed objects covering all data sources involved of any types (RDBMS, XML, etc.).
- Stable string object identifier to refer from anywhere; back reference navigation is supported;
- XQuery/XPath-like ES-Path language to query the whole tree.
- Remote entries are cached locally; no stale data is possible.
- No central messaging server needed to notify of changes; increased scalability.
- Effective network data interchange
Entry Service: http://www.fusionsoft-online.com/entryservice.php
|
|
|
|