On 17-10-12 18:15, Gregg Wonderly wrote:
It depends on what you are tracking. I always put my ServiceItems in
a map, keyed by ServiceID. That map then has values which are maps
of LUS to ServiceItem. I really never use ServiceItem for anything
except a holder of the trio of values, because with multiple LUS on
the network, you really need to hold a reference to all ServiceItems
to be ready to deal with transient LUS behaviors.
ServiceDiscoveryManager does similar things for you.
I was expecting a somewhat pre-cooked solution from SDM, the
datastructure you describe looks similar to SDMs internal structure.
When you have just a list, the loss of one LUS will cause the
disappearance of all services, instead of possibly none.
You really need more than a list and equals!
You are right. Presenting this data not only involves rendering in the
sense of which and how Entries are presented, but also reductions of
multiple SI into 1 line to present to the user.
