1. No - you would have to totally re-process all the packets. 2. Not that I'm aware of 3a. Because it was crap, easily broken and hard to maintain. 3b. Yes 4. Um... as long as you can implement the c-style call back interface, sure. No clue if perl can do this, but think about performance -- you're running a lot of packets through a plugin on a busy system.
A while back I had proposed an events interface as a adjunct to the plugins. I'm still thinking it's something I would like to do, but haven't started work yet. It would disappear if you didn't want it and if you did, all the key points in the ntop code would be instrumented to queue an event for a thread to process async (session start, session end, new host, etc. etc. etc.) You'll first see my XML interface dropped in, maybe today. It's stable, I'm just burning in a new processor. But I'll put that into a separate msg. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Hicks Sent: Sunday, September 29, 2002 10:11 AM To: [EMAIL PROTECTED] Subject: [Ntop] Half OT, but it's a weekend.... [ntop]/MySQL <snip /> Back on the ntop front, I've been considering doing something to restore MySQL support since I already use MySQL to store a lot of our historic records. I'm wondering if anyone would be willing to share some sage advice on how ntop and mysql relate. 1) Would it make sense to do MySQL integration as a plug-in? 2) Has anyone started anything like this already? 3) What was the motivation in ripping the mysql support out? Would looking at what was ripped out do any good or harm? 4) Can plug-ins be written in perl? Have any been? _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop
