[
https://issues.apache.org/jira/browse/FELIX-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239573#comment-14239573
]
Carsten Ziegeler commented on FELIX-4720:
-----------------------------------------
Modularity enables choices, so I can pick the best log service implementation
for my needs and I can pick the best web monitoring tool, the web console, and
it might happen that this log service implementation does not provide a history
but is blindly fast and makes good coffee. And then the web console support for
the log service is useless. But I want good coffee and this support...
I think we can add a configuration option to the web console plugin which will
buffer the entries and not rely on the history of the log service
implementation, disabled by default. If the log service impl of the history is
crap, hit the switch and enjoy. No chance for current users, but it helps
everyone who likes that kind of coffee.
But to be honest, I have the feeling we're spending more time into discussing
this issue than it would need to actually solve it :)
> Web Console and Gogo rely on Log history buffer in the Log Service
> ------------------------------------------------------------------
>
> Key: FELIX-4720
> URL: https://issues.apache.org/jira/browse/FELIX-4720
> Project: Felix
> Issue Type: Bug
> Components: Gogo Command, Web Console
> Reporter: Peter Kriens
>
> The OSGi Log Reader Service has a command to get the history of the log.
> However, the specification states that this history can be empty. The Equinox
> framework is nowadays registering a Log Reader Service that has such an empty
> history to prevent pinning objects in memory.
> Using the history this way was always at odds with the specification since
> the history was only intended to hold the start up events. The primary model
> of the Log Service is a dispatcher.
> I suggest that the Gogo log command and the Web Console maintain their own
> history buffer to become independent on this fragile history buffer in the
> Log Reader service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
