Hej, 2010/2/19 Frank Silbermann <[email protected]>: > 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.
That is a very strict definition that doesn't include hybrid applications using Google Gears or a combination of HTML5 and JavaScript. I think the definition is too strict. > 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.) Building an application two times with different technology does not feel like a very efficient way. But I would guess that Wicket's server side state approach works contrary to the technologies used for building offline web applications. Bye Hauke Ingmar --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
