From: David Talbot <dtalbot@reallinx.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: TC Point & Click + XML
Date: Fri, 13 Jul 2001 13:27:26 +0000 [thread overview]
Message-ID: <marc-lartc-99503103513932@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99499934900884@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
This would be wonderful... is it an OS project (And how far along is
it)? It always seemd to me that things like routing and rate limiting
rules would be better described by a configuration file than by a series
of command line commands.
-David Talbot
Michael T. Babcock wrote:
>On 12 Jul 2001 17:41:42 -0500, Nikolai Vladychevski wrote:
>
>>But what I am trying to do is to release it for
>>production where the end users would point & click for filter creation &
>>bandwidth definition, so I think it will be an adventure, but I am
>>accepting the risks... after all.... it's free code....
>>
>
>I've been working on an XML format for describing a traffic control
>configuration in-house. We're working on a good way to describe the
>rules and its not too hard since most of the settings are hierarchial.
>We've eliminated the need for specifying parents by the inherentness of
>nesting classes under cbq queues and queues under classes, but have a
>few more things to iron out. I'll be posting what we come up with and
>some code to turn it into TC statements when its more stable unless
>there's outside interest in working on it.
>
>Offering users a point-and-click QoS+TC environment was on our minds
>when we realised that what we needed was a good configuration file
>format to save the settings in.
>
[-- Attachment #2: Type: text/html, Size: 1654 bytes --]
next prev parent reply other threads:[~2001-07-13 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 4:41 [LARTC] Re: TC Point & Click + XML Michael T. Babcock
2001-07-13 13:27 ` David Talbot [this message]
2001-07-13 15:22 ` Michael T. Babcock
2001-07-13 15:53 ` Togan Muftuoglu
2001-07-13 18:49 ` David Talbot
2001-07-13 20:21 ` Michael T. Babcock
2001-07-13 22:04 ` David Talbot
2001-07-15 1:40 ` Michael T. Babcock
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-99503103513932@msgid-missing \
--to=dtalbot@reallinx.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.