netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo@netfilter.org>
Cc: Netfilter Development Mailing list
	<netfilter-devel@vger.kernel.org>,
	rwhite@pobox.com, neal.p.murphy@alum.wpi.edu
Subject: Re: [PATCH nft] src: deprecate "flow table" syntax, replace it by "meter"
Date: Fri, 24 Nov 2017 15:03:02 +0100	[thread overview]
Message-ID: <20171124140302.GA21727@salvia> (raw)
In-Reply-To: <CAOkSjBgPMs=xWGYWizam9ttPRKJQyj9Frj1dmB2fcu7J47yp+g@mail.gmail.com>

On Fri, Nov 24, 2017 at 01:13:10PM +0100, Arturo Borrero Gonzalez wrote:
> On 23 November 2017 at 15:23, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > According to bugzilla 1137: "flow tables" should not be syntactically
> > unique.
> >
> > "Flow tables are always named, but they don't conform to the way sets,
> > maps, and dictionaries work in terms of "add" and "delete" and all that.
> >
> > They are also "flow tables" instead of one word like "flows" or
> > "throttle" or something.
> >
> > It seems weird to just have these break the syntactic expectations."
> >
> > Personally, I never liked the reference to "table" since we have very
> > specific semantics in terms of what a "table" is netfilter for long
> > time.
> >
> > This patch promotes "meter" as the new keyword. The former syntax is
> > still accepted for a while, just to reduce chances of breaking things.
> > At some point the former syntax will just be removed.
> >
> > Closes: https://bugzilla.netfilter.org/show_bug.cgi?id=1137
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> >
> 
> I agree.

Thanks, I just sent a few more patches to incrementally address what
this is describing.

> What about adding a warning in case of using the old syntax?
> Something like:
> 
> WARNING: this syntax is deprecated and will be deleted in the future,
> use 'meter' instead.

We can probably make a patch to add warnings on all things that we
plan to deprecate.

There are more things that we're just taking from the grammar to avoid
sudden breakages, it would take a bit of time to review the existing
grammar and spot them with a warning too.

After that, make a new 0.8.1 release asap, including --with-mini-gmp
fix if possible.

      reply	other threads:[~2017-11-24 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 14:23 [PATCH nft] src: deprecate "flow table" syntax, replace it by "meter" Pablo Neira Ayuso
2017-11-24 12:13 ` Arturo Borrero Gonzalez
2017-11-24 14:03   ` Pablo Neira Ayuso [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=20171124140302.GA21727@salvia \
    --to=pablo@netfilter.org \
    --cc=arturo@netfilter.org \
    --cc=neal.p.murphy@alum.wpi.edu \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=rwhite@pobox.com \
    /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;
as well as URLs for NNTP newsgroup(s).