Hi
Guy Harris wrote:
Pilz Rene wrote:
From the logical point of view it makes sense to put this
functionality into libpcap. But in the next
step it would be necessary to change the format aswell, because it is
too weak. Something like ERF
is already better, but still not there where I want to be.
http://www.tcpdump.org/pcap/pcap.html
The next release of libpcap probably won't write that, but I'd like to
get code in that'll read it, or at least read the subset that the
current libpcap API can handle (and just ignore the parts it can), so
that the release after that can write it without writing files that no
older release can read.
This new format looks promising. I will take a closer look at it and try
to get into contact with the developers.
So I ask myself if it is still a good place to put it.
Yes, it is.
With this new format: Yes. Small things which are missing now can be
added easily afterwards via options.
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
/rene
--
Dipl-Ing (FH) MSc. C.E René Pilz
ftw. Telekommunications Research Center Vienna http://www.ftw.at
Tech Gate Vienna, Donaucitystraße 1, A-1220 Wien
Mobile: +43 664 8269871 Office: +43 1 5052830-13 Fax: +43 1 5052830-99
