atom feed16 messages in org.apache.incubator.sling-devRe: Annoyance during update of bundles
FromSent OnAttachments
Alexander KlimetschekAug 29, 2008 7:50 am 
Tobias BocanegraAug 29, 2008 11:33 am 
Alexander SaarAug 29, 2008 11:58 am 
Jukka ZittingAug 29, 2008 12:17 pm 
Alexander KlimetschekAug 30, 2008 1:58 am 
Carsten ZiegelerAug 30, 2008 2:15 am 
Tobias BocanegraAug 30, 2008 9:47 am 
Felix MeschbergerAug 31, 2008 10:58 pm 
Bertrand DelacretazSep 1, 2008 12:04 am 
Alexander KlimetschekSep 1, 2008 12:54 am 
Felix MeschbergerSep 1, 2008 2:02 am 
Alexander KlimetschekSep 1, 2008 2:16 am 
Carsten ZiegelerSep 1, 2008 2:31 am 
Alexander KlimetschekSep 1, 2008 3:05 am 
Felix MeschbergerSep 2, 2008 1:15 am 
Bertrand DelacretazSep 2, 2008 4:14 am 
Subject:Re: Annoyance during update of bundles
From:Carsten Ziegeler (czie@apache.org)
Date:Aug 30, 2008 2:15:14 am
List:org.apache.incubator.sling-dev

We have discussed a related feature:

https://issues.apache.org/jira/browse/SLING-490

Volunteers? :)

Carsten

Alexander Klimetschek wrote:

On Fri, Aug 29, 2008 at 8:33 PM, Tobias Bocanegra <tobi@day.com> wrote:

how about stalling requests until the update is complete ?

Good idea. This would also save one from all the other problems you can get (html node render servlet triggered, jsp compile errors, etc.).

But I am not sure if this is what you want in a production system - if you have high traffic and most requests don't use the servlets or services provided by the bundle that is updated. Maybe it's possible to stall only requests to the servlets that are provided by the bundle in question.