True, it shouldn't boil down to convenience while categorizing defects and
enhancements!
Iam unsure about significant benefits like reduced search complexity atleast in
the case of LOG service lookups, but yes LOG can be optimized to not perform
avoidable lookups.
Also, i seem to have now learnt that the complexity/effort involved in fixing
this in IMM is significant.
On this topic, we seem to be wanting to choose an option that is less complex
but also help the user. We can only hope that there are no active users who are
performing similair searches, because they wouldn't be ready to re-compile
their test code!
Also, similair optimization needs to be done in other middleware services,
atleast in AMF AFAIK.
Finally, I guess there is a workaround to handle this scenario in the older
releases, which is to enable the environment variable in nid.conf itself.
---
** [tickets:#1452] LOG: Use root name when searching for stream objects**
**Status:** review
**Milestone:** 4.7-Tentative
**Created:** Fri Aug 14, 2015 12:34 PM UTC by elunlen
**Last Updated:** Mon Aug 17, 2015 09:17 AM UTC
**Owner:** elunlen
At startup the log server searches for stream configuration objects. The search
is done with no root object defined (NULL pointer for rootName in parameter).
Search root should be "safApp=safLogService".
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
