Ethereal-dev: Re: [ethereal-dev] Re:

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: Ashok Narayanan <ashokn@xxxxxxxxx>
Date: Mon, 5 Jul 1999 17:16:12 -0400 (EDT)
Laurent Deniel writes:
 > Jeffrey Perry wrote:
 > > 
 > > Yes, one comment. I think this is the right approach, I would suggest
 > > taking it one step farther though. If you build the parser into
 > > ethereal, then no recompiles would be needed for adding a new
 > > protocol. This is how Etherpeek on Windows works.
 > > 
 > 
 > Yes, I like this approach also.
 > 
 > I was already thinking about the handling of user-defined protocols in
 > a similar way but with direct processing in ethereal (no code generation
 > and so no recompilation - see some previous posts in mailing list).

Given that we are an Open-Source project and the source code will
always be available for compilation, is this really useful? I can see
in a closed-source project the ability for users to extend the sniffer 
without giving them the source code could be useful, but I am not sure 
how this model extends over to Open Source.

-Ashok


-- 
--- Ashok Narayanan ----------------------------------------
IOS Network Protocols, Cisco Systems
250 Apollo Drive, Chelmsford, MA 01824
Ph: 978-244-8387