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

[Guy Harris <guy@xxxxxxxxxx>]

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

> Can we add these to the "logfiles" or "tutorial" department, so
> people can see what ethereal can do for CORBA.

The "'logfiles' department" would, I guess, be the "Sample Captures"
page:

	http://www.ethereal.com/sample/

although presumably we'd have to add a note about building the dissector
for "echo.idl", as standard Ethereal will just dissect the common GIOP
part.

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.

> //
> // Basic IDL to excercise many IDL types.

	...

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