[omniORB] On The Wrie Protocol/Filename offset

[Tran, Thomas H]

Hi Duncan Grisby,

I need to do it base on IDL definition. I am study your dump.py code, unfortunately I don't know python so I am readying Python on the web right now.  Once I learn python, I would like to step into your dump.py code line by line. Is there an IDE or tool you recommend me to use. I hope that is possible.

I am also look at lex/yacc route. I was playing with lex/yacc about 15 years ago. I wonder if I can get the lex/yacc file spec for IDL then modify the output to generate my offset.  

I am in window environment. I am wonder omniorb backend or lex/yacc route is less complicated for newbie.

Thanks
Tom


-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Wednesday, August 08, 2012 3:21 AM
To: Tran, Thomas H
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] On The Wrie Protocol/Filename offset

On Tue, 2012-08-07 at 10:18 -0700, Tran, Thomas H wrote:

> How would I programmatically create a table of fieldname/offset of 
> CORBA-IDL structure on the wire?

Do you want to do it based on the IDL definitions, or at run-time?

If you want to do it based on IDL, you have to compile the IDL into a suitable structure. You can do that by making a new back-end for omniidl. See

  http://omniorb.sourceforge.net/omni41/omniidl.html

If you're asking because you're sniffing the traffic and want to decode it, you might find Wireshark's idl2wrs helpful. It's a back-end for omniidl that builds a Wireshark plugin:

  http://www.wireshark.org/docs/man-pages/idl2wrs.html


If you're trying to do it at run-time, look at the CORBA::TypeCode interfaces to see how to dynamically find out about a type definition.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --