Re: JavaClient offline storage / replication
Re: JavaClient offline storage / replication
- Subject: Re: JavaClient offline storage / replication
- From: Stamenkovic Florijan <email@hidden>
- Date: Wed, 15 Apr 2009 12:55:51 -0400
On Apr 15, 2009, at 12:42, Chuck Hill wrote:
On Apr 15, 2009, at 9:36 AM, John Huss wrote:
On Wed, Apr 15, 2009 at 11:25 AM, David Avendasora <email@hidden
> wrote:
On Apr 15, 2009, at 11:51 AM, Stamenkovic Florijan wrote:
On Apr 15, 2009, at 11:24, John Huss wrote:
We're considering using JavaClient for some new projects and one of
the big features we want is the ability to run offline by caching
database from the server's DB and storing any modifications locally
until the server is online again. How would you approach this? Is
it possible to use the same EOModel and use EOF on the client to
save the data locally?
Your way: no. You are not allowed to do this. You can only
distribute the client-side libs in your client app, and those do
not contain the functionality to connect to whichever data-source
(EOAccess).
I'm not entirely sure this is true anymore. If you can deploy a
standard WO app to any platform for free, why can't a "client"
machine run the same stuff as a "server"? I know that when it cost
money for a deployment license, they specifically said you could
send the client-side apps to a client for free. But now that the
whole thing is free... why not?
Yeah, I agree. The license permits you to bundle WO with your
server application. The only restriction is that you can't use the
bundled WO frameworks to develop new applications on the machine
you're deploying it too -- not a problem.
So what then? If all of WO is available on the client... Still
seems tough.
I didn't know about these licensing changes. Sorry for the out-of-date
info. Need to read up about what's allowed nowadays, and what not.
And tougher still if the data you are caching can get modified on
the server while the client is disconnected. Then you have some
interesting update conflicts to handle. This can be a real tough
nut to crack.
Yeah, data freshness in general would be a pain. However one would
handle it, some serious confusion for the users is inevitable. The
only reasonable way out of this that I can see is to make the cached
data read-only.
F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden