TAO and other CORBAs are basically implemented in accordance with the specification 2.6 provided in OMG. The basic prototype, basic data definition, IDL language syntax, and C code mapping, etc. We can see the familiar methods and data structures definitions in the implementation of the code (probably the bottom level and high-level), such as the ORB of the OMG CORBA specification, and PoA, basically give ORB core, POA object adaptation realizes the prototype frame. To understand a CORBA's entire system, there must be a general understanding of CORBA's specifications. This is greatly helpful for implementing CORBA code understanding. It plays a framework for CORBA, understanding and understanding code. Implementation will mention higher levels. The Corba specification can be said to be its skeleton, and the implementation is hematopoietic and meat.
TAO is based on ACE, which is developed in which many of them reflects the thinking of ACE and its extension. Therefore, the understanding of TAO is a platform role in the understanding of the familiarity of ACE. Essentially ACE is a communication library, and it is also a semi-finished library of writing, ACE is a powerful platform for TAO. In fact, the ACE communication library makes the tao code easy to understand and divide, and ACE is more reflected in the details of the details and control package, shielding the easy-to-error code on the upper layer, putting hardware platform and implementing detail packaging In the underlying code (the OS.h code of ACE accounts for 10% of the code); the TAO is more in the far process call to achieve logically around the CORBA specification; this Tao's CORBA code is The ACE communication library is very clear, communication and CORBA implementation logic a certain degree of coupling is weakened, making TAO code to be easily understood and mastered than other CORBA implementation code. When I first saw TAO's code, I was a headache. It was a deep understanding of ACE. Although the time of contact was also long, I stayed at a level of concept and primary applications, and I didn't experience the library code of ACE. . With yourself, you can see your own source code and you write your own communication library (many concepts from ACE and another CORBA implementation orbcus) and simple far process call implementation, from the problems and problems to solve, Considering the problem, the problem to be achieved, etc., to deepen the essential thinking, and found that the final return to the issue of Corba to solve, he is doing someone else, and seeing to do better, actually Corba has already Propose and solve and implement industrial grade methods. I have seen things that don't actually do these from the new "Invention Wheel". I really understand some of the understanding of CORBA. I am still very helpful to be a "wheel". At least there is a deeper understanding of some problems. . This also has a role in understanding the implementation of TAO. They are all realization of far process calls, and simple concept is complex, but basic common things are similar, but in achieving tao has strong and exquisite, look at the immersed, I can do it? .
