Hi there JUGgers!
I'm new around here... Both on the count of the JUG and on the count of
Java...
But I've taken on the ambitious tasks of doing a major development in
Java.
I have a java developer on board, but need to get some advice.
Here's what I'm need.
1. Webpages that link to a database for transactioning.
2. Both the code and the data must be available offline (on the client)
3. No manual client side install may be required. Ie a browser prompt
to install some code is fine, but no "insert the CD, bla, bla, bla..."
I chose Java, since it allows applet caching virtually automatically,
provided the JRE is installed.
However, as explained somewhere else already, the following also
applies.
(I've copied the mail I replied to somewhere else... instead of
retyping it
all)
> If you're looking for an off-line based application, PHP / MySQL etc
> are probably not going to work unless the client also runs a web &
> database server and the web content and databases are mirrored between
> the two when he is online.
>
> But just a question - what database backend are you actually looking
> at ?
We're basically committed to PostGreSQL. (unless there's a good reason
to change - it's not too late yet)
> I can understand running the applets on the client-side, but what
> database do they connect to ?
We are planning to find/build a caching engine that caches the cruicial
data (a few tables only) on the client side. The client then always
reads a local cache database of some sorts and the engine refreshed the
data.
> Or are you using the XML-based java database engines ?
I was considering this, but was led to believe that it's very slow?
> Or must the client be able to edit data etc and simply "upload" this
> to
the web server
> when he comes on-line again ? AFAIK, cachning will work for the Java
> Applets but not for the data changes / edits etc.
Your assessment is correct, although the client must lookup a status
for a member. Based on that info, a claim is submitted (for which
another lookup is required to determine the diagnoses code.
Here's a little diagram that I'm considering.
+------------------------+
| Applet in Browser |
+------------------------+
^
|
v
+------------------------+
| Local Data cache |
+------------------------+
^
|
v
+------------------------+
| Datapump |
| (Keeps the whole |
| lot synchronised) |
+------------------------+
^
|
v
(((( internet ))))
^
|
v
+------------------------+
| Web Application Server |
+------------------------+
Thoughts? I somehow think I'd be re-inventing the wheel with this, but
can't find the other wheel someone somewhere has built already...
regards
Roland Giesler
