- **status**: review --> fixed
- **Comment**:

default(4.6):

changeset:   6333:9ecba23b4059
parent:      6331:04c0bc58f3d1
user:        Zoran Milinkovic <[email protected]>
date:        Thu Mar 12 17:02:22 2015 +0100
summary:     imm: add new API functions for replacement SaNameT with SaStringT 
[#643]

changeset:   6334:a783a4f4adcb
user:        Zoran Milinkovic <[email protected]>
date:        Thu Mar 12 17:03:22 2015 +0100
summary:     imm: service support for replacement SaNameT with SaStringT [#643]

changeset:   6335:d9cee12a1a8f
user:        Zoran Milinkovic <[email protected]>
date:        Thu Mar 12 17:04:13 2015 +0100
summary:     immtools: support for replacement SaNameT with SaStringT in IMM 
tools [#643]

changeset:   6336:2ab6613d52b3
tag:         tip
user:        Zoran Milinkovic <[email protected]>
date:        Thu Mar 12 17:04:53 2015 +0100
summary:     immtest: add tests for replacement SaNameT with SaStringT [#643]



---

** [tickets:#643] IMM: API that replaces SaNameT with SaStringT and 
SA_IMM_ATTR_DN**

**Status:** fixed
**Milestone:** 4.6.FC
**Created:** Thu Nov 28, 2013 05:00 PM UTC by Anders Bjornerstedt
**Last Updated:** Wed Mar 11, 2015 07:14 AM UTC
**Owner:** Zoran Milinkovic

The IMM service should provide an updated API where all use of the troublesome
SaNameT type is replaced by the SaStringT type or the SaConstStringT type #625.
Also needed is a new flag value for attribute definitions: SA_IMM_ATTR_DN. 

Defining an attribute in an IMM class definition on the SaStringT type and
also setting the flag SA_IMM_ATTR_DN, will mean that the attribute is intended
to hold a value that should be a DN. 

Other flags that make sense to also set on such an attribute definition where
applicable are:

    SA_IMM_ATTR_RDN if this is the RDN attribute. Just as having SaNameT the 
    type of an RDN attribute indicates that the class is an association class,
    having SaStringT and SA_IMM_ATTR_DN combined with SA_IMM_ATTR_RDN would 
    also indicate that this is an association class.

    SA_IMM_ATTR_NO_DANGLING. Currently (OpenSAF 4.5) is only allowed 
    on attributes of type SaNameT, but will of course be allowed also on
    attributes of type SaStringT if the SA_IMM_ATTR_DN flag is also set.
    The exception is the RDN attribute which still can not have the 
    SA_IMM_ATTR_NO_DANGLING set. The reason is that the RDN atribute, 
    even if defined on SaNameT, or on SaStringT with SA_IMM_ATTR_DN flag,
    actually does not contain a simple DN value. The RDN attribute of an
    association object contains a value on the form X=Y where the right hand
    side is a DN. Strictly speaking the logical type of an RDN attribute
    is never a simple DN/reference, even if the type is SaNameT. 

All the other flags may also be used in combination with SA_IMM_ATTR_DN, with
the normal meaning. 






---

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.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to