I haven't looked into Gears at great length, but I think you may be up against a wall here - where the two may be incompatible. Offline gears applications require fat clients. Wicket isn't typically for making fat clients because everything about it ties it back to the server.
If you already have it such that each office has their own server and database, then it seems that this isn't a product development problem so much as it's a network support issue. How often should the network within an office really be down? I'd try to push this problem back up the management chain. Conceptually, it's a cool idea, though. Let us know if you have any success. -- Jeremy Thomerson http://www.wickettraining.com On Fri, May 1, 2009 at 3:04 AM, Carlo Camerino <cmcamer...@gmail.com> wrote: > Hi, > > Is there any project which has Wicket And Google Gears Integration? > Wicket has really done a lot of us in speeding up development time. Coming > from a struts we saw the power of Wicket in terms its reusability and i've > noticed that > wicket already did most of the tasks that we would have to manually do using > struts application, like session timeouts, redirects, etc.... > > One of our main concerns however are that clients > are asking for our applications to be available even if the network is down > or if the central server is down.. > Currently we implemented our applications in a distributed fashion wherein > every branch ( Remote Location) has its own server. > However, this has implications of cost and administration issues. > However, if offline mode is enabled we can just begin syncing right. > > I think that Wicket WIth Google Gears Application will make it even better . > > > I think this is really a plus when it comes to marketing it to customers. > Most of the applications that we create our banking applications and any > downtime is costing our clients. > > Hopefully we can also do this to offload the central servers and to put > processing into client machines. > > One large problem I see though is that most code wil have to be moved to the > Browser Layer. > I'm thinking of how to create a wicket application which is mostly run by > java classes work on the client side. > Looks as if there will be a lot of code changes... > I'm not really sure if it would be a totally different programming model. > > Anyone out there tried to integrate Gears And Wicket > > Carlo > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
