| Supporting the Register directive comes in two flavors; lets call them
Simple and Complex. For v1.2, we elected to support 'Simple'
Registration for the Sample AM.
'Simple' Registration means that the Management Module can translate
the Fullname Identifier to Primary Identifier by itself.
Registration FM Sample AM
--------------- ----------------
Register Sample .molar Show Sample .molar All Identifiers
The requirement we put on the fullname identifier for the Sample AM is
that the "Last Simple name is really the phase4 name"
So, ".molar" as a fullname translates to "molar" as a phase4name
and ".lkg.tan.wakeme" translates to "wakeme"
After the Sample does the translation, it is business as usual.
----------
'Complex' Registration means that the Management Module can not
translate the fullname by itself. It has to look into DNS to get the
translation from fullname to primary identifier.
The Registration FM will call your 'show identifers' routine with the
fullname so you can return your list of identifiers - but you will have
to DNS to get the translation ... and you haven't been registered yet!
So - you must implement the REGISTER directive yourself. The
Registration FM will see that you have a primary identifer and call
your register directive with fullname as the in-entity, and In-P
containing the other identifiers .. you tuck the other identifiers into
a cache, and return
When the show identifiers directive comes in, before going to DNS you
check the cache - and find the data - and return it. Then the
registration fm puts the data into DNS - and sets up the back
translation (primary identifier to fullname link).
----------
Whew - so, how many of you did I loose? All this information will be
properly documented in the Toolkit and Registration FM Module Reference
Manuals (MRM).
/keith
|