[
https://issues.apache.org/jira/browse/FELIX-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855315#action_12855315
]
Felix Meschberger commented on FELIX-1141:
------------------------------------------
> My experience showed that using such "back-channel" is performance drawback.
Right, I did not see it from that angle, so lets drop the idea of a
"back-channel"
> IMHO a better optimization is to update how these request are handled.
Yes. We can (and should) definitely optimize here, in fact, what could be the
side effects:
* bundle stop -> only the stopped bundle's state changes to stop or exception
is thrown
* bundle uninstall --> only the stopped bundle's state changes (actually it
should be removed from the list) or exception is thrown
* bundle start -> this might have side effects on other bundles in they
become resolved
So, for start/stop/uninstall we might in fact just return the new bundle state
or the exception and just update the bundle entry on the client side (ignoring
any side effects on other bundles due to bundle start)
This would reduce the data (either new state or exception) and the requests (a
single request)
WDYT ?
> Provide feedback for operations
> -------------------------------
>
> Key: FELIX-1141
> URL: https://issues.apache.org/jira/browse/FELIX-1141
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Reporter: Felix Meschberger
> Attachments: bundle-operation-error-feedback.patch
>
>
> Currently the Web Console does provide almost no adequate feedback for
> operations like bundle installation, bundle start, configuration save, etc,
> etc. We need a way to provide such feedback to the client. This is a bit more
> tricky since many operations actually are executed in the background like
> actual bundle operations.
> I see this issue as a broadening of the feedback request in FELIX-1061
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
