Hi
Some thoughs from me, too :)
On Mon, Jul 22, 2002 at 10:15:23PM +0200, Giorgio Zoppi wrote:
> > said in past mails, I plan to remove database support from ntop. This is
> > because:
> > - ntop is too fat
> > - database support (as of today) is suboptimal
> > - ntop must export information in a better way.
> Why not export all info in XML and create a small parser as contrib application,
> which is able to fetch XML and put on DB? XML is good only for metadata apps.
XML is nice but it would be far to much overhead in my opinion.
I would rather use sFlow (or netflow) as standard output and provide
daemons that store it or export it converted to yet another format.
The problem is that external programs can only work with the data ntop
exports so I'm unsure if there's already a protocol that transmits every
information ntop could give.
Wouldn't it be better to enhance the current module structure to build
a customized ntop daemon? The advantage would be that the modules could
take direct use of the internal structure of ntop.
If using a kind of chaining or hook mechanism (thinking of Apache and
Proftpd) one could even compile two or three different exporters in.
The nice GUI could then become it's own module and only activated on
demand.
bye,
-christian-
--
Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0
[EMAIL PROTECTED] Internet & Security for Professionals Fax 0241/911879
WESTEND ist CISCO Systems Partner - Authorized Reseller
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://lists.ntop.org/mailman/listinfo/ntop
