Well, this sounds very confusing, but I couldn't find a better title for that, might be I am not good at that! Whatever!! :-) Well the problem was, we had a problem :-) we called it dynamic library update problem. The program at the client side is made up of a bunch of shared objects (.SOs) and obviously a binary. But a set of classes in binary kept changing every now and then, hence this resulted in upgrade of the binary and eventually the installer every time, and that too dynamically (on runtime). Hence, this very well known design came in picture with a bit of change. For clarity of the problem and the solution this is the simplest picture which one can see. A binary with a class which kept changing very frequently. To overcome the problem the classes "which kept changing" are pulled out of the binary, and bundled into a shared object. On top of it created an Abstract class which can be accessible in binary as well as the "so". Shared object