Internet names and name spaces

The presumption is that sockets.c has a front ent symbol table:

Listen socket_addr mysock port;

mysocket here is under namespace control, and socket.c has a front end symbol table, like all the snippits. My approach is that data manager has constructed the set of mysock names and ports such that is can also be the call back to deliver data to listener. sock_addr here is whatever horrid syntax is required by tcp/ip, and not under the control of data manager, except at the deeper ip layer. 

So we have a systematic approach to names and call backs. We can use the same idea with sockets t consent and io manager to xchars. The binding is tight and fast, the focus is on improving name technology, not call set up. And we expose systematic name space control down to the terminal functions. The industry adds by making the import and using functions afford  data manager an opportunity for redirection, mainly implementing the uniqueness rules. N individual syntx engine know the enterprise name space.