On first impression, this looks very nice - I think you got the object
hierachy figured etc; i will look closely later.
What would be really interesting is to see (gulp) a SOAP/xml interface
on top of this. Is this something you can do with those "bindings"?
It seems to me from a library perspective, youa nd Thomas may have to
sync. And restricting to just QoS maybe be a limitation (netlink is the
friend you are looking for; so from networking perspective, give them 
GUI clikers ways to set routes, static IPSEC SAs etc). Oh and it would
be interesting to have events (see that link come up down etc)

cheers,
jamal

On Fri, 2005-02-11 at 10:07, Dan Siemon wrote:

On Wed, 2005-26-01 at 08:48 -0500, jamal wrote:

quoted

Your call really - you are the one who is going to maintain it;->
As for ease of use and avoiding users from knowing details of how
tlvs are put together etc - i think it doesnt matter how thats done
underneath the hood; it is still doable on top of current libnetlink. In
other words whats required, IMO, is something that hides netlink totaly
so that the programmer/user doesnt even get to see TLVs.

(Sorry to join this thread so late.)

I'd like to make a little plug for my Linux QoS Library (LQL) [1]
project.  LQL provides an abstraction of the kernel QoS features.  Full
API documentation is available from the website.

I already have working bindings for one high level language (C# on Mono)
[2]. Creating bindings for Python, Perl etc should be quite easy.
Someone recently emailed me about starting work on Perl bindings.

There is still lots of work to do.  Support for more QDiscs and
classifiers is needed and the socket handling code needs a rewrite to
better handle errors.  Work continues and these things will be fixed.

[1] - http://www.coverfire.com/lql/
[2] - http://www.coverfire.com/lql-sharp/