[
https://issues.apache.org/jira/browse/CXF-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113787#comment-14113787
]
Akitoshi Yoshida commented on CXF-5582:
---------------------------------------
Hi Sergey,
thanks for your comments.
I thought of getting rid of the refresh button and thought about what would be
a good user-experience. There are several questions. The first question is the
user's anchor point. The page, the entry, or dynamic. To explain this, let's
say we are at the last page showing the most recent entry at the bottom of that
page and the new entries are continuously (periodically) added below. As the
number of entries on that page is limited, the older entries will disappear
toward the top and be pushed to the preceding pages (or in other words, you
will see them again when you move to the preceding pages). In this case, if you
stay on the last page, you will see the actual new entries without switching
the pages. We can call this the page-anchored mode. The user is anchored at a
specific page and the entries move up and toward front as new entries are being
added. This is convenient if you keep watching the latest entries but
distracting if you want to look around one specific event. In contrast, in the
entry-anchor mode, we add new entries below and when the page gets full, add
them in the following pages. You will see those newly added entries when you
first move to those pages. And we can combine these two by using the
page-anchored mode when you are at the bottom of the last page but by using the
entry-anchored mode anywhere else. In this case, those who are interested in
the latest events can stay at the last page and those who are interested in a
particular event can stay on the page containing that event. In any case,
updating a multi-page bounded table may be a tricky thing.
In either case, I think we basically don't need the refresh button but may need
it to freshly re-sync the feed content.
Your ideas of multi-windows sounds very good. Having one or more separate live
windows to directly show the latest or important events will be useful and
promissing.
Maybe, we can create and try out several client apps.
regards, aki
> Enhance CXF LogBrowser to receive Log events in real time via WebSocket
> ------------------------------------------------------------------------
>
> Key: CXF-5582
> URL: https://issues.apache.org/jira/browse/CXF-5582
> Project: CXF
> Issue Type: Improvement
> Components: Management
> Reporter: Sergey Beryozkin
>
> CXF Log Browser is GWT based and can be used to monitor log events on
> per-endpoint basis.
> The user registers CXF endpoints in the left-side pane and can see the
> per-endpoint specific log events in the right pane, but the user can only get
> these events by initiating the browser to poll the endpoints, by pressing
> "Refresh" button.
> The browser should be able to receive real-time log notifications via Web
> Socket and show them to the user.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
