[omniORB] Is it imperative to keep client and server interface in sync?

Rolf C Stadheim rcs at bgoark.no
Wed Jan 7 17:32:36 GMT 2004


I was wondering how important it is to keep the stubs and skeletons in sync,
between client and server?

That is, suppose one have the following original interface:

mudule test
{
    interface someObj
    {
           void someMethod1();
    }
}

The stubs and skeletons for the client and servant (both C++) are generated,
and all is well.

Now suppose the interface gets one more method:

mudule test
{
    interface someObj
    {
           void someMethod1();
           void someMethod2();
    }
}

and the stubs are generated, and the client is compiled and linked with
these new stubs. The servant is unchanged.

Now, if I use this new client, but only call the original someMethod1() (the
servant naturally does not know anything about someMethod2()), what are the
consequences, if any?

Access violation, systems exception, or will this work fine as long as the
client does not call the new method?

Regards,
Rolf C Stadheim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040107/6b716805/attachment.htm


More information about the omniORB-list mailing list