Luis EG Ontanon schrieb:
SQL clients are blocking. (There may be some non-blocking, but I'm not
aware of any GPL compatible non-blocking SQL client). That means that
wireshark should wait for the write to be acked before capturing the
next packet and that would probably cause many packets to be dropped,
thus rendering the whole thing useless.
There's nowhere mentioned, that it has to be done "online" :-)
IMHO Off-line scripting is the way to gets packets into a database.
Yes, but the main question Guy noted is still valid: Which database
schema to use?
Without a good idea what to do with the database data, it's pretty
pointless to put it into the database ;-)
Luis
On 8/3/07, Juan José Navamuel <jnavamuel@xxxxxx> wrote:
Is there any news regarding this topic in the Wishlist?
Data I/O (e.g. Files)
1.
The ability to dump packet data/info into an SQL database. (How
would the schema for the database be specified, and how would the
information to be dumped to the database be specified? A change
that hardcodes a particular schema and set of data to be dumped
would be of limited use. -/Guy Harris/)
Thanks a lot!
--
====================================================
Juan J. Navamuel
Instituto Tecnológico de Aragón (ITA)
Address: María de Luna 8, 50018 Zaragoza (Spain)
Phone: +34 976 71 62 50
Fax: +34 976 71 65 39
URL: http://www.ita.es
e-mail: jnavamuel@xxxxxx
====================================================
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
