Ethereal-dev: [Ethereal-dev] Ethereal as "front-end" (was: SQL patch)

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

From: Tom Uijldert <Tom.Uijldert@xxxxxxxxxxxxx>
Date: Fri, 31 Oct 2003 14:43:03 +0100
Hi list,

This is what I understand from the SQL discussion that is going on:

There is a basic need for nifty post-processing of data that is captured and
interpreted by Ethereal.
One wants to use the dissecting- and filtering capability to get the proper
data and subsequently...
-	put it in a relational database to, for instance, relate it to other
data
-	put it in a spreadsheet to get nice graphs (as can be found under
the "Tools" menu)
-	etc.

I vaguely recall a similar discussion on csv-files and spreadsheets some
months ago (Ronnie?).

Isn't it time for an "export" function or module that can do these things?
Whereby one could choose what protocol(s) to export, what fields and what
packets?
A first preference would be to export CSV, as there are a lot of
applications (including the Oracles of this world) that can readily import
such data.
Or indeed export XML-data or INSERT TABLE-statements...

Or am I *way* off the mark here?

Btw., I think Biot Olivier's contribution is an entirely different
discussion. In that case we're talking about being able to filter using a
different language, namely SQL.

Thanks,
Tom Uijldert          Email: Tom.Uijldert [at] logicacmg.com