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.

From: Frank Singleton <frank.singleton@xxxxxxxxxxxx>
Date: Mon, 09 Jul 2001 07:03:20 -0500
Hi,

See my comments below.

/Frank

Craig Rodrigues wrote:
> 
> On Fri, Jul 06, 2001 at 01:36:11PM -0500, Frank Singleton wrote:
> > Hi,

<snip>

> >
> >
> > 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?
> 

Yes that how it works at the moment.

> 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.


Yep, but I would like to add some "core" CORBA services
anyway :-)

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

I will take a look at this..

Has there been prior discussions about using protocol"families".

ie: During say "autogen.sh" one can elect to
include a family of dissectors or not, based on
their relationships. Basically allowing you to 
build subsets of ethereal , tailored for  different
environments.

eg: I want the following family of dissectors only.

ethereal-core, (whatever that may be)
ethereal-giop-all
ethereal-rpc-all


Cheers / Frank..

-- 
EUS/SV/Z Frank Singleton      ASO Americas BSS
Office : +1 972 583 3251      ECN 800 33251  
Mobile : +1 214 228 0874      Amateur Radio: VK3FCS/KM5WS   
Email : frank.singleton@xxxxxxxxxxxx

Hardware: HP Omnibook 4150 running Redhat Linux 7.1 (2.4.3-12 kernel).