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]
