ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Ethereal-dev: Re: [Ethereal-dev] Re: [Ethereal-users] Ethereal binary for Sharp Zaurus (fwd)

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

From: Guy Harris <guy@xxxxxxxxxx>
Date: Fri, 14 Mar 2003 11:02:42 -0800
On Fri, Mar 14, 2003 at 12:15:35PM +0100, Philippe Biondi wrote:
> - put every packet-*.c sources in their own directory !

That's a lot of directories:

	hostname$ ls packet-*.c | wc -l
	     328

Why do they *need* to be in their own directories?

> - The simultaneous use of wiretap and libpcap does not help clarity.
>   There are callbacks, callback wrappers, and so on..

Well, that's not likely to change, at least not in the sense of ceasing
to use one of them.

Libpcap doesn't have an API to allow it to be made into a full
replacement for Wiretap; doing so would be a significant amount of work.

Wiretap isn't likely to include replacements for the packet-capture code
in libpcap, as that'd mean that there'd be two separate packet capture
libraries that'd both have to be maintained.

However, at some point, Wiretap might have a packet capture API
implemented by calling libpcap.