Ethereal-dev: Re: [Ethereal-dev] IDL file and matching GIOP log

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: Frank Singleton <frank.singleton@xxxxxxxxxxxx>
Date: Tue, 17 Jul 2001 14:36:09 -0500
Guy Harris wrote:
> 
> > 2. je6.log - A logfile
> 
> Presumably meaning "a capture"; I think of a "logfile" as a text file
> logging messages - we call captures of network traffic "captures".
> 
Yes, a capture file.

> I guess "echo.idl" itself would go into the "doc" directory, along with
> a note in "doc/README.idl2eth" mentioning that it's a sample IDL file,
> and noting that there's a capture for that protocol on the Ethereal Web
> site in the "Sample Captures section.
> 

I will update doc/README.idl2eth

> 
> > module Penguin {
> >
> >
> >   interface Echo {
> 
> Hmm.
> 
> Should either of *those* names, rather than the name of the file, be
> used as the protocol name by "ethereal_be.py", so that you don't get the
> protocol name changing if the file name changes?

I have had similar thoughts.. to make it the name of the 
"top level" module.  Maybe the next patch .....

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