We are exposing the functionalities of a large system as CORBA services. As we build IDL, the question comes up:
should we use more than one namespace in our IDL, i.e., having nested "Module"?
Currently everything is under one Module. I am wondering the pros and cons of having sub-namespaces so that each
functionality group belongs to one sub-namespace. (We are using C++ to implement CORBA services)
Since the IDL modules get mapped to C++ namespace, which is not intuitive if you have a few in your system. I hesistate
to use more than one namespace. In fact, I donot see the advantage of nested namespaces in IDL other than avoiding name
collision (which we can avoid with a little caution).