Ethereal-dev: Re: [Ethereal-dev] GIOP Subdissector plans

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Craig Rodrigues <rodrigc@xxxxxxxxxxxx>
Date: Fri, 6 Jul 2001 18:11:34 -0400
On Fri, Jul 06, 2001 at 01:36:11PM -0500, Frank Singleton wrote:
> Hi,
> 
> Ok, time to leverage the GIOP code and idl2eth written
> thus far.
> 
> In order to make available many of the standard CORBA
> IDL defined services available for decode, I propose
> the following naming scheme for GIOP subdissectors.
> 
> 
> CosNaming.IDL   =>    packet-giop-cosnaming.c
> CosEvent.IDL    =>    packet-giop-cosevent.c

Hi,

I think all this CORBA dissector work you 
have done is really cool.
I still don't understand one thing though:
Do you require a separate dissector for each
IDL file?

If so, then the fact that you are choosing
the standard CORBA services (Naming, Event, etc.)
is a good start, but this could start getting out
of hand as people add more dissectors for their own
interfaces.

Does Ethereal have the capability to load dissectors
from a 3rd-party shared library?

It might be nice to be able to put all the 
CORBA IDL dissectors in a separate directory, and
compile them into a shared library which could
be optionally loaded into Ethereal at run-time.

The size of the Ethereal binary is getting quite
large now with all the dissectors being contributed.
-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@xxxxxxxxxxxx