> > - The whole interface must take care of the byte order issues. This is
> > the most tricky part.
> I don't see how byte order issues are a problem when using SOAP.
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 changes. A
generic partly binary based protocol will have byte order issues.
My current idea, given I can't find an existing protocol, is to let
every netlink user describe its own format with a generic grammar so
the protocol can stay stable. One of the candidates is the netconf
specification which basically does what we need but is still in early
> I'm curious exactly what your needs are.
Basically I need to be able to change the beavhiour of the message
parser to for example overwrite the sequence number checking in order
to do message multiplexing. It's not like I would be represenative
> It does appear you are aiming for a somewhat more low level library than
> I am. Whether or not that precludes some kind of merger I don't know.
Yes, it seems so. It's a pitty that we waste effort by doing the same
nearly work but I really need the low level API and the possibility to
customize the parsing and sending code.