
Signature
______________________________
Remove "_SPAM" to reply directly.
It appears to me that in your quest to make the 2-tier fat-client work to
your satisfaction, you are missing the advantages of the 3-tier
client-server architecture.
Here is what you could have with the backend server handling the database
access and business logic:
1. The client could be synchronized (assuming that this means loading some
or all of the table's rows into the client's volatile memory) automatically,
by a callback from the server. This callback would come if and when and the
table's content changes, forcing the affected clients to re-synchronize,
without bothering the user. This, of course, is beneficial only in the
multi-user environment, with multiple clients accessing the same database
concurrently. If all your client needs is its own private database, then why
worry about synchronization in the first place?
2. The database connection, login and password, as well as formatting and
submitting the queries to the database, can be handled by the server, with
the client sending the initial request (not necessarily in the form of an
SQL statement) to, and getting the results back from the server. In this
case, the sensitive login info is never exposed to the client.
3. Updating the client's front-end could be handled by the server, again in
a fully automated way. The client would check with the server at the launch
time, if the client's executable files (JARs in the case of Java) are
obsolete, and if yes, then download the updated JARs from the server and
restart.
These concepts, along with other things, have been implemented in our
product, STEP FORWARD. If you are interested, have a look at
www.gestalt.com.
Alex Molochnikov
Gestalt Corporation
403-252-3282
> Hello folks,
>
[quoted text clipped - 34 lines]
> ______________________________
> Remove "_SPAM" to reply directly.
David Shorthouse - 15 Nov 2005 08:10 GMT
Alex and others,
Indeed, I understand your suggestions. In doing a bit of reading these
past few days, I have crystallized my needs. What I want is a Java-based
smart client with an embedded database because:
1. clients need to work offline
2. clients need to upload records to backend when online (synchronization is
not needed, merely the ability to upload new or changed records via simple
sql queries; i.e. the client need not receive anything in the way of data
from the backend)
3. from my perspective, being able to push UI updates or announcements from
an application server is certainly attractive
Can anyone point me in a direction where something like this can be done. I
came across Servoy (www.servoy.com), which is exactly the sort of thing I
would like to use because of its simplicity, but the offline smart client
capabilities mention using that development package are cryptically
described at best.

Signature
______________________________
Remove "_SPAM" to reply directly.
> It appears to me that in your quest to make the 2-tier fat-client work to
> your satisfaction, you are missing the advantages of the 3-tier
> client-server architecture.