What is your need for knowing the internal architecture of our iControl implementation? All you should need to know is the single endpoint that acts as a proxy for all method implementations:
https://bigip_address/iControl/iControlPortal.cgi
We make use of a pluggable shared library architecture to enable facilitate licensing, etc. The *Handler.so files are SOAP-CORBA marshalling libraries that convert the SOAP calls into CORBA calls to our backend CORBA server.
Again, I'm interested in what brings you to even ask this as it should be completely transparent to the iControl user.
-Joe
Nimbostratus