[Ns-developers] ns-3.4 action plan

[Tom Henderson]

Raj Bhattacharjea wrote:

> 
> ----Object Naming System----
> The names discussion has wound down, and Craig's repository is
> undergoing testing for merge within a few days.

There have been two changes to the above repository recently, based on 
some discussion I had with Craig.  The first is to allow the "/Names/" 
prefix to be omitted in most places, to improve readability.

i.e. this used to be the required syntax:
   Names::Add ("/Names/server", n.Get (1));

but this is also equivalent now:
   Names::Add ("server", n.Get (1));

The only place you cannot use this shortcut is in the Config commands, 
because that system always expects a fully qualified path name:

   Config::Set ("/Names/server/eth0/Mtu", UintegerValue (1234));


The second change is to allow objects to be renamed:

   Names::Rename ("node0", "access-point");

Rename() will facilitate future auto-naming of objects.  In particular, 
if helper classes are configured to name objects automatically (as I've 
suggested before), there may be a desire to replace an auto-generated 
name with a more meaningful name.

I think that the above is ready for merge.  I think it would be nice if 
we could configure the helpers to optionally add names to certain 
objects (particularly devices), such as a convention that all Csma 
NetDevices automatically end up with names like "eth0", "eth1". 
Attached is the start of a patch along these lines.  I think that the 
auto-naming can be built on top of what Craig already has, in the helper 
classes, so I do not want to suggest holding the merge of what is 
already there to work on autonaming-- I am just bringing it up as food 
for thought.

- Tom
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: names.extension.patch
Url: http://mailman.isi.edu/pipermail/ns-developers/attachments/20090203/3368b1aa/names.extension.ksh