From: Harald Welte <laforge@gnumonks.org>
To: Thomas Graf <tgraf@suug.ch>
Cc: Michael Buesch <mbuesch@freenet.de>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: WCONF, netlink based WE replacement.
Date: Fri, 20 Jan 2006 09:48:29 +0100 [thread overview]
Message-ID: <20060120084829.GW4603@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20060113131503.GA379@postel.suug.ch>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
On Fri, Jan 13, 2006 at 02:15:03PM +0100, Thomas Graf wrote:
> * Michael Buesch <mbuesch@freenet.de> 2006-01-12 18:24
> > This is an attempt to rewrite the Wireless Extensions
> > userspace API, using netlink sockets.
> > There should also be a notification API, to inform
> > userspace for changes (config changes, state changes, etc).
> > It is not implemented, yet.
>
> I'll only comment on the netlink bits and leave the rest to
> others. I'd highly recommend the use of attributes instead
> of fixed message structures to allow the interface to be
> flexible to extensions while staying binary compatible.
I can only second Thomas' suggestion. The power and flexibility of the
use of netlink is only really unveiled if you use attributes. This way
you can easily extend your data structures later on without breaking
compatibility, etc.
--
- Harald Welte <laforge@gnumonks.org> http://gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-20 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 17:24 Michael Buesch
2006-01-13 13:15 ` Thomas Graf
2006-01-20 8:48 ` Harald Welte [this message]
2006-01-13 17:55 ` Stephen Hemminger
2006-01-13 23:23 ` Pavel Machek
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=20060120084829.GW4603@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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
all inboxes | Powered by JetHome®