On a more global note:
One might say "why not just use 'tcpstream' on the captures?", except
that:
> > What I've got so far is limited to TCP stream analysis and is basically a
> > partial reimplementation of tcptrace-style time-sequence, throughput and
> > RTT graphs. It can do zooming in and out, crosshairs, a kind of "magnifying
> > glass" where you temporarily magnify portion of graph, you can select
> > packets in ethereal's packet list by clicking on segments on graph and so
> > on.
so, in fact, the graphing code does actually interact with the rest of
Ethereal.
However, that brings up a broader question:
Can we make it more convenient to extend Ethereal in ways
*other* than adding support for new protocols?
Some possibilities might include:
embedded extension languages;
some kind of object-based scripting interface along the lines of
what I understand ActiveX and Bonobo's scripting interface to
offer (does KParts offer anything like that?).
(Yes, ActiveX is Windows-only, and Bonobo would require GNOME, and any
KParts scripting mechanism would require KDE, so we might end up either
having to roll our own scripting interface or adopt something else, or
arrange to have, in addition to "generic" Ethereal, Windows-specific or
GNOME or KDE variants thereof implementing the scripting interface in
question.)
