Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] API using cbq / tc ?
Date: Sun, 09 Feb 2003 13:39:07 +0000	[thread overview]
Message-ID: <marc-lartc-104479804408967@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104453716713244@msgid-missing>

On Sunday 09 February 2003 04:45, Ming-Ching Tiew wrote:
> Haha life is a trade off between want you actually
> want and what you actually get. I like the java
> approach too but it will take me donky years
> to complete the same functionalities, and you might
> say it is due to my incompetencies. LOL
:)
But I like the freedom.  You can do something, I can do something, and we are 
al happy.  But I hope mine solution will be better :)  (without competion 
there is no innovation)

> There are other considerations which I have consider
> too. Small footprint is a No 1 item here. The
> floppy-based firewall/nat router can't house a
> http server anyway, so a small footprint daemon
> is needed. Eventually you are talking about something
> like a MRTG approach where the daemon collecs raw
> data and handle over to MRTG on  another computer
> for html data processing/presentation.
>
> If anyone like this approach, he could enhance the
> fwstat.pl (based aleady in the package )to provide
> qdisc/class traffic to MRTG. Feel free and do it !
I already did.  But that gives only longterm statistics.  For real time 
statistics, you need the data directly from the router.  

I prefer a cross-platform solution.  Even if it means that you loose some 
functionality.  It's possible that VB is better/handier then java, but I go 
for java.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-02-09 13:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:20 [LARTC] API using cbq / tc ? Srikanth
2003-02-07  2:28 ` S Mohan
2003-02-07  4:37 ` Srikanth
2003-02-07  7:44 ` Stef Coene
2003-02-08  7:02 ` Ming-Ching Tiew
2003-02-08 10:39 ` Stef Coene
2003-02-08 13:04 ` Ming-Ching Tiew
2003-02-08 13:22 ` Stef Coene
2003-02-09  3:45 ` Ming-Ching Tiew
2003-02-09  7:26 ` Henry Yen
2003-02-09 13:39 ` Stef Coene [this message]
2003-02-10  1:58 ` mingching.tiew
2003-02-10  8:59 ` Stef Coene
2003-02-10 18:01 ` Jay Wineinger
2003-02-10 18:20 ` Stef Coene
2003-02-11 16:59 ` Martin Devera
2003-02-11 18:16 ` Stef Coene
2003-02-12  8:29 ` devik
2003-02-12 17:45 ` Stef Coene
2003-02-13  8:30 ` devik
2003-02-13 10:36 ` mingching.tiew
2003-02-13 18:39 ` Stef Coene
2003-02-13 18:40 ` Stef Coene
2003-02-14  3:58 ` mingching.tiew

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-104479804408967@msgid-missing \
    --to=stef.coene@docum.org \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox