Peer Client Update in Lava Distributed SQL

Probably the largest difference between Lava Distributed SQL and conventional databases is the fact that clients are kept up to date with the latest data in all distributed tables, typically within a few seconds of modification by another user. This, coupled to a second facility in the Distributed Client (described below), yields a very interesting possibility for applications build on Lava Distributed SQL.

Client Update Notification

The Lava Client has a facility specifically targeted at client applications which aim at being more informative to the user. The application may set up notification criteria through a Lava function, which configures a nominated message to be sent to the application when updates within a given schema or to a specific table arrive from the Primary Server.

Any number of these notifications may be configured, each with its own message if so required.

GroupWare

Using this notification system, the client application can automatically refresh displays or post user messages in order to inform the user of modifications to data tables he is busy with.

It is also possible to monitor which user in the network is currently busy with which data elements (row locking status is also communicated to each client) allowing the application to prevent simultaneous modification of data by two or more users. Graphical or colour attributes may be modified to keep track of data element status, informing the user on a second-by-second basis of activity in the database.

Using these options, the application designer may build in comprehensive GroupWare capability with very little effort or complication.