From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: RFC: NAT configuration over ctnetlink
Date: Fri, 12 May 2006 18:41:45 +0200 [thread overview]
Message-ID: <4464BAC9.7010600@trash.net> (raw)
In-Reply-To: <446476B9.7060505@netfilter.org>
Pablo Neira Ayuso wrote:
> OK, I'll finish the patch then. I'm thinking about hiding the definition
> of nfct_conntrack/nfct_tuple/... and provide the getters to access the
> attributes of the object. Since this structure could evolve in time, we
> wouldn't have any problems to introduce new changes in future. But that
> would definitely break code that initialize the structure by setting up
> the structure fields. Ideas?
I don't think thats necessary (and I'm no fan of hiding things unless
there's a good reason), basically all of these structures are similar
to semantically well-defined structures in the kernel that are very
unlikely to change in an incompatible way.
prev parent reply other threads:[~2006-05-12 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 6:46 RFC: NAT configuration over ctnetlink Patrick McHardy
2006-04-29 15:39 ` Pablo Neira Ayuso
2006-05-02 14:06 ` Patrick McHardy
2006-05-02 16:51 ` Pablo Neira Ayuso
2006-05-02 17:10 ` Patrick McHardy
2006-05-02 23:32 ` Pablo Neira Ayuso
2006-05-03 13:40 ` Patrick McHardy
2006-05-10 19:16 ` Harald Welte
2006-05-11 7:05 ` Patrick McHardy
2006-05-12 5:41 ` Patrick McHardy
2006-05-12 11:51 ` Pablo Neira Ayuso
2006-05-12 16:41 ` Patrick McHardy [this message]
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=4464BAC9.7010600@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.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.