Conference azur::mcc

373.0. "Full or partial DNS entity specification?" by KETJE::PACCO () Tue Oct 02 1990 16:25

    As from what I understand, it's advised to use subdirectories of DNS to
    register entities.
    
    I tried to specify a full DNS name, e.g.
    
    MCC> Register BRIDGE  namespace:.mcc_bridges.mybridge
    
    This register command accepts this register command, but tried to
    register on the local default DNS namespace, instead on the specified
    one, in our case NAMESPACE:.
    
    This is very confusing.  The error I got was  DNS$ACCESSDENIED, where I
    had all privileges to write in my own NAMESPACE:.  It took me a lot of
    time to understand the MCC was trying to write to the default (DEC:)
    namespace....
    
    Is this a bug or the expected behaviour ?
    
    Note:  I would appreciate the use of a logical name which, if defined,
    would be used to store, access etc... all entities of a certain class.
    e.g.
    
    if MCC_BRIDGE is assigned to NAMESPACE:.MCC_BRIDGES
    the command
    MCC> Register bridge mybridge
    
    would automatically register thie bridge as
    NAMESPACE:.MCC_BRIDGES.mybridge
    
    The same kind of logicals as e.g.
    for stations	MCC_STATIONS	NAMESPACE:.all_stations
    for nodes		MCC_NODE	NAMESPACE:.dna_nodes	(as it is
    today) etc...
    
    Also this default location should be modifiable through the FCL and MAP
    PMs.  In the MAP PM this "prefix" should appear automatically in front
    of the place where the entity specification must be entered to include
    this entity e.g. in a domain.
    
    Regards,
    Dominique.

    I tried some tests.
    
    The registration accepts full names, and works as per the names given.
    Please check your Name space set up once more ! If the problem persists
    let us know. I will be glad to look into.
    
    
    Jesuraj
    

   The Iconic Map only supports the "default" namespace.  If
you try entering the namespace when adding the entity, it removes the 
"NAMESPACE:." portion.   

/Jim

    ref.2.
    
    Is that a bug or a feature ??
    
    
    jesuraj

This is a bug!   Any good citizen in the DNS arena should allow for
access to multiple namespaces with the default namespace assignable
by either using the DNS current clerk default or allowing the initialization
procedure, a set default command, or the specification of a namespace
nickname to override the clerk default.   /Claudia

  For v1.1 it is a "feature" (read: thats the way we are planning to
ship it cos we don't have time to add the support).  If anyone feels that 
the product should NOT be shipped without support of more than one 
namespace, send me mail.

Thanks
/Jim