What you describe here is different than what was implied by your first comment.
What you now seem to be asking is this. Please verify: You have multiple install sites (satellite offices, etc), and each of them has a server that runs the application on its own. Users from that location will connect to that server (i.e. users in the Dallas office connect to the Dallas server, NYC users to the NYC server, etc). You want Dallas to be able to go "offline" - that is, disconnected from NYC, but you want the Dallas users to still be able to use their application at their location while the two offices are disconnected from each other. If this is the case, then it's not a Wicket question - it's a database question. Basically you need a database that will handle multiple master configuration where one master is still able to function without connectivity to the second. I haven't looked at this for quite some time, but I'm sure you can find some resources out there describing it. I know at ApacheCon last year, the CouchDB guys were promoting the fact that you can use CouchDB in such a situation. However, I'll warn you that if you come from a typical relational database background, CouchDB may not be your cup of tea - and you'd probably have a hard time selling it within your company. You'll just need to find someway of doing multi-master replication with a traditional DB server. -- Jeremy Thomerson http://www.wickettraining.com On Fri, Feb 19, 2010 at 7:38 AM, Josh Kamau <[email protected]> wrote: > I was thinking that i could install the same application on each site, then > have the databases synchronized somehow. My CTO will have me for lunch if i > suggest this. > > On Fri, Feb 19, 2010 at 4:26 PM, Frank Silbermann < > [email protected]> wrote: > > > Any application that executes _offline_ is not a _web_ application -- > > unless the system consists of a stand-alone application containing a web > > server that runs on the client (e.g. via jetty) so that both client and > > server are running on the same box. > > > > Theoretically, a Wicket application that runs on a jetty server on the > > client could synchronize itself, when possible, via non-Wicket web > > services that run on the server. > > > > But why go that route? I'd build just an ordinary stand-alone client > > application, e.g. using Java WebStart and Swing, that could optionally > > connect to the server. There's no need for Wicket on the server, since > > the client would provide the user interface. (The client would have to > > do that, if it were to be able to run stand-alone.) > > > > > > -----Original Message----- > > From: Josh Kamau [mailto:[email protected]] > > Sent: Friday, February 19, 2010 7:05 AM > > To: [email protected] > > Subject: Offline capable web application > > > > Hi guys; > > > > I am working on an application that i want to enable to work offline. I > > want > > to use wicket for this. Any ideas. I would like uses to fill and submit > > forms even when working offline and then the data is synchronised later. > > Is > > it possible? all manner of suggestions/links are welcome. > > > > Regards. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
