Because we found out that some users were complaining about "bugs" which were in fact cause by au buggy proxy with caching enabled (external to our web app) and so we would like to be able to force all clients to reload their resources from the server side without any service disruption. We don’t mind if the modification takes 5 minutes to be fully active but we don't want to lose users connected to a server during the change (session replication is not enabled so a restart / redeploy causes our users to be switched to the backup server and "disconnects" them).
To achieve that a solution would be to be able to change tapestry's app-version which would cause resources path to be rewritten and re-downloaded. Regards Thomas -----Message d'origine----- De : Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Envoyé : jeudi 11 août 2011 15:33 À : Tapestry users; Belot Thomas Objet : Re: Is there a way to change "tapestry.application-version" value without redeploying the webapp ? On Thu, 11 Aug 2011 09:20:50 -0300, Belot Thomas <thomas.be...@santeos.com> wrote: > This is what I thought ... does anybody think this would be a good idea > or should I just forget it ? Why do you want to change it? -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br
