On Tue, Sep 2, 2008 at 10:15 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...What you are looking for are messages of the form BUNDLE STARTED
(which comes after BUNDLE UPDATED) or FrameworkEvent PACKAGES
REFRESHED, which comes at the end of the installation/update
If we include a
On Sat, Aug 30, 2008 at 11:15 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
We have discussed a related feature:
https://issues.apache.org/jira/browse/SLING-490...
The plan in that issue was to compute the Sling ready flag once and
have it set forever, but it might be useful to allow the flag
Hi,
Alexander Klimetschek schrieb:
Hi all,
when I update a bundle containing a servlet (eg. servlet path =
/bin/myservlet) and I hit my curl command for testing that servlet
(POST to /bin/myservlet + a few specific params) too fast, ie. in the
time when the old version of the bundle is
On Mon, Sep 1, 2008 at 11:02 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
This is of course also a possible scenario in a live environment, esp.
in environments used globally: Imagine an IT department in USA updating
the bundle while a user in Germany tries to use the service ...
How about
I'm wondering what we really want to achieve here and if it is worth the
effort?
For production systems this is imho more a non-issue, as you usually
don't update directly a productive machine.
For development you know that you updated a bundle and shouldn't send
new requests during the update.
On Mon, Sep 1, 2008 at 11:31 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
I'm wondering what we really want to achieve here and if it is worth the
effort?
For production systems this is imho more a non-issue, as you usually
don't update directly a productive machine.
For development you
Hi,
Jukka Zitting schrieb:
Hi,
On Fri, Aug 29, 2008 at 8:33 PM, Tobias Bocanegra
[EMAIL PROTECTED] wrote:
how about stalling requests until the update is complete ?
This does probably not really work. Let me explain:
* What do you do if the update fails ? You cannot keep the
system
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
[EMAIL PROTECTED] wrote:
how about stalling requests until the update is complete ?
Good idea. This
On 8/30/08, Alexander Klimetschek [EMAIL PROTECTED] wrote:
On Fri, Aug 29, 2008 at 8:33 PM, Tobias Bocanegra
[EMAIL PROTECTED] 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
Hi all,
when I update a bundle containing a servlet (eg. servlet path =
/bin/myservlet) and I hit my curl command for testing that servlet
(POST to /bin/myservlet + a few specific params) too fast, ie. in the
time when the old version of the bundle is gone, but the new version
is not yet started,
Am 29.08.2008 um 16:50 schrieb Alexander Klimetschek:
Hi all,
when I update a bundle containing a servlet (eg. servlet path =
/bin/myservlet) and I hit my curl command for testing that servlet
(POST to /bin/myservlet + a few specific params) too fast, ie. in the
time when the old version of
how about stalling requests until the update is complete ?
regards, toby
On 8/29/08, Alexander Klimetschek [EMAIL PROTECTED] wrote:
Hi all,
when I update a bundle containing a servlet (eg. servlet path =
/bin/myservlet) and I hit my curl command for testing that servlet
(POST to
Hi,
On Fri, Aug 29, 2008 at 8:33 PM, Tobias Bocanegra
[EMAIL PROTECTED] wrote:
how about stalling requests until the update is complete ?
That would also make startup time when a number of bundles are just
being loaded much more predictable. Currently you just need to wait a
while until all
13 matches
Mail list logo
