OK, I think you means in PyWireTap or other python wrap class, can't
export internal information or structure about ethereal's wiretap
implmentation. That's is also my expected, with a dynamic script
language like python, we can isolate the wiretap's API changing. So I
define the interface follow the python style, that is amazed agility.
Thanks :D
On Thu, 18 Nov 2004 18:59:43 -0800 (PST), Guy Harris <gharris@xxxxxxxxx> wrote:
> Flier Lu said:
> > Thanks for your advice, I think I could update PyWireTap to lastest
> > wiretap. but the best choice is merge it into ethereal, maybe not only
> > PyWireTap but also Python, like some other open source tools, use
> > python as build-in language. :D
>
> Merging it into Ethereal won't prevent it from breaking third-party
> applications if the Wiretap API changes; it'll just prevent PyWiretap from
> breaking when the Wiretap API changes.
>
> When I said "Be aware that the Wiretap API is not frozen at this point and
> is subject to change (and might change significantly once the
> next-generation libpcap format starts being used).", I wasn't warning that
> PyWiretap would break if the API changed, I was warning that any
> application that *uses* PyWiretap would break if the API changed, so
> providing something that explicitly exports that API might encourage
> people to write software that won't continue to work with future Ethereal
> releases.
>
>