Hi Mathi,
I am not sure what you are referring to by "the complexity/effort of fixing
this in the imm".
I am not aware of any problem in the IMM that needs fixing in relation to this.
So I am not sure how the non existent fix is complex or not.
The IMM supports long DNs if the config variable is set and does not support it
if it is not set.
The IMM must not be configured for long DNs if there is some component in the
deployment that can
not tolerate long DNs and that is implemented so that it inevitably encounters
long DNs if they exist in the system.
That is how it is specified and documented..
There is no way around that, i.e. no "fix" in the IMM for a problem that
resides with applications that can not
tolerate long DNs yet wants to do global lookups.
/AndersBj
From: Mathi Naickan [mailto:[email protected]]
Sent: den 17 augusti 2015 14:11
To: [opensaf:tickets]
Subject: [opensaf:tickets] #1452 LOG: Use root name when searching for stream
objects
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]<http://sourceforge.net/p/opensaf/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 you indicated interest in
https://sourceforge.net/p/opensaf/tickets/1452/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
---
** [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 01:03 PM 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 http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://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
