Performance/Development question

[Robert Laing <rlaing@xxxxxxxxx>]

I have a database running on our 8.0.1 Domino server that serves as a 
central source of information for several other databases.  When documents 
are updated in this particular database, I need to update other databases 
with that information on an almost real time basis.  I had coded these 
updates into the QuerySave event of the primary forms.  For local users, 
this update process is negligible.  For remote users, the update process 
takes way too long.  For various reasons, we cannot utilize local replicas 
for these remote users, nor can we bump up the bandwidth.

One option I was considering was take the update out of the QuerySave 
events and make a scheduled LotusScript agent that runs every 15 minutes 
or so that will take the changes in the main database and update the 
secondary databases.

Another option I was considering was to code a Java program that would run 
on the iSeries, wake up periodically and handle the updates.

Performance is a concern in this environment.  Any opinions on whether it 
would be more efficient to have a frequently running LotusScript agent on 
the Domino server or a frequently running Java program running outside the 
Domino environment but manipulating Domino objects ???

Thanks in advance,

Bob