(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 avail
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 o
I've been looking at this before and I do like your approach. The license prevents me from really using it buts that's not your problem. What I really like about it are the bindings to other languag
Yes, a SOAP/XML-RPC interface should be quite possible. This is one of the main reasons I went to the trouble of creating the Mono bindings. I need to create some sort of XML interface to LQL in the
* Dan Siemon <1108246033.7554.18.camel@ganymede> 2005-02-12 17:07 Before you go ahead, please consider its possible usages. If possible it should conform to an existing format allowing for distribute
The initial implementation will be very specific to LQLs methods. I need this for a prototype application. I don't see how byte order issues are a problem when using SOAP. Example? My main design goa
It depends on wehther your outline every qdisc/filter in the protocol. If you do so it's not a problem but you have to extend your protocol every time a new qdisc is introduced or an existing one ch
Perhaps we could agree on a single API for the low-level message parsing and netlink message construction. At least then we would not be duplicating bug-fixes in our netlink code. Whether or not this
Sure, I think they're quite similiar. I abstracted the netlink message and routing attributes building a bit and added some bits for simplification. http://people.suug.ch/~tgr/libnl/doc/group__msg.h
Sorry, for the tardy response. That could be a problem. The GObject struct must be at the start so that all sub-classes can be operated on with the g_object_ functions. The only way to make these obj
It's not a problem, as you note we can put the gobject information into NLHDR_COMMON. I'm not focusing on such bindings but if you want to reuse my code, feel free.
ormance numbers for the ematch changes I realized that the throughput of changes per second is almost only limited by the cost of starting the tc binary over and over. In order t