[omniORB] Specification of IDL for communication

[Johnny Willemsen]

Hi,

This sounds tricky, the marshaling of a boolean if as a single octet,
but changing the struct definition does change the typecode of your
type. Maybe it works, but I wouldn't recommend it.

Best regards,

Johnny Willemsen
Remedy IT
Postbus 81 | 6930 AB Westervoort | The Netherlands
http://www.remedy.nl

On 07/05/2016 12:32 PM, 上畠克仁 via omniORB-list wrote:
> Hi.
> 
> I am creating a communication application using the structuredescribed
> in IDL language.
> And, omniORB was also used for development of this application.
> 
> Currently, there is communication application working well.
> And I'd like also to communicate with the application that I am going
> to create newly.
> At this time, the difference between the application currently working
> and the new is that data type of one in the member of the structure is
> different, but each other's size is the same.
> (This structure is used as a parameter of the remote function.)
> 
> The reason that changed data type in new application is because it
> wanted to increase the information that can be the structure has.
> 
> Would this communication be guaranteed in this case?
> (Can this new application communicate with old application ?)
> 
> 
> Specifically, I am trying to communicate in a structure as follows.
> 
> //Currently working
> struct structureA {
>         string     name_;
>         boolean    jugement_;
>         boolean    reserved_;  *1 *2
> };
> 
> //Newly creating
> struct structureA {
>         string     name_;
>         boolean    jugement_;
>         octet        newValiable_;  *2
> };
> 
> *1 In this structure, 'reserved_' is not used yet.
> *2 This is used between the new things, but it isn't used by the thing
> currently working.
> 
> 
> Any advise is very appreciated.
> Thanx.
> 
> K.Kamihata.
> ===============================================
> YDC Corporation.
> name: Katsuhito Kamihata
> mail:  katsuhito_kamihata at ydc.co.jp
> ===============================================
> 
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
> 
>