TABLE OF CONTENTS In this appendix we look at certain implementation details of Mico. This appendix is intended for readers who want to understand the inner workings of Mico. Additionally, it should provide a good starting point for system programmers who want to understand, extend, or modify certain parts of Mico.
We begin with a trace of a method invocation through Mico, since that gives a good overview of the interplay of the various components of Mico. We then discuss how to add new invocation adapters, new object adapters, and new transport protocols to Mico. The appendix will be concluded with a section on the structure of the program code generated by the IDL compiler.
This section follows the path an operation invocation takes from the source (client) to the destination (server), using the "Account" client introduced in Section 3.4 that calls a deposit operation on the server. As already illustrated in Figure 6.4, the method invocation first passes the SII, the ORB, and the GIOP client in the client process. The GIOP client generates a message that is sent to the server. There, it is received by the GIOP server, passes through the ORB and the object adapter, and finally results in a method invocation on the skeleton of the target object. The results of the method invocation return to the client on the reverse route. The following important classes are involved in the execution of the method invocation in the...
