[brussels-dev] [networking-discuss] Architectural requirements behind lib*adm...

[Paul Durrant]

Darren Reed wrote:
> On  7/04/09 02:05 AM, Paul Durrant wrote:
>> ...
>> The majority of code, rather than being put in usr/src/cmd/dladm.c was 
>> put in usr/src/lib/libdladm.c to create an API so that other tools 
>> could use it if so desired.
> 
> Was there any input from anyone outside of the team that created dladm 
> as to how those functions should be named and the interfaces designed?
> 

Nope. The initial functionality of libdladm was minimal. We had quite a 
bit of input as to how the various subcommands of dladm should be named 
and I tended to follow that guidance in naming the functions in libdladm 
i.e. there was basically a one-to-one mapping between dladm subcommands 
and libdladm functions.

 > Was there any thought as to what those other tools might be or how it
 > would be expected for them to use that library?
 >

My only thoughts at the time was that there might be a GUI one day.

   Paul

-- 
===================================
Paul Durrant
http://www.linkedin.com/in/pdurrant
===================================