I’m sure you two have thought about this quite a bit,
but I’m curious why you haven’t implemented
Hierarchical session names?
And also ORing of views?
In comparision to say, log4j hierarchical loggers.
Why do i see a need?
I have a large subsystem in my application,
say ‘X’, and if I give it one session name, I cannot easily filter X’s subcomponents output.
For example, maybe X has three phases (X.A,X.B,X.C) which generate copious output. If I give a
single session to X, I cannot easily generate a view
for A,B, or C.
But if I give A,B, and C individual sessions,
I must generate a special view to see all of X.
(and maintain it when I later add X.D)
But, hierarchical names would allow easy selection of X and its children, or any individual child.
And if the ability to ‘OR’ views with checkboxes is present, users how a lot of power to select what is visible.
Although not near as strong as SI, the log4j viewer
’LogMX’ can be used to experience a heirarchical
oring session/logger type selection mechanism.
But, I’m clear SI is the best of breed in the market,
and appreciate having it.