Creating named filter groups, and support enabling/disabling them

[GoogleCodeExporter]

For IISpeed we received multiple feature requests for being able to name a set 
of filters, and enable/disable  filters within those sets by their respective 
names. Having such a feature could reduce the amount of typing needed by 
reducing duplication in configuration. But  it might also allow naming sets of 
filters that would be safe to use with product x.

Does this sound gererally useful enough to have in psol?
If so - I could implement it and patch it back.

Original issue reported on code.google.com by osch...@we-amp.com on 8 Jul 2013 at 9:31

[GoogleCodeExporter]

I'm a little worried about overly enriching the configuration semantics.  That 
can have high overhead.

I'd also like to point out that Apache 2.4 has a reasonably rich macro language 
which -- for that platform -- might be a better way to solve this problem.  The 
typical Apache solution is to put a configuration you want to re-use in 
multiple vhosts in its own configuration file and Include that from each vhost 
that needs it.

Are there similar platform-specific approaches that can be used in nginx & IIS?

Original comment by jmara...@google.com on 22 Jul 2013 at 2:46

[GoogleCodeExporter]

See also: Issue 689

Original comment by jmara...@google.com on 22 Jul 2013 at 2:49

[GoogleCodeExporter]

Re: "Are there similar platform-specific approaches that can be used in nginx & 
IIS?"

Both nginx and IIS are able to include files in configuration like Apache does. 
Sounds like a simple and sound solution to me. 
Thanks!

Original comment by osch...@we-amp.com on 23 Jul 2013 at 9:14

[GoogleCodeExporter]

Original comment by sligocki@google.com on 25 Jul 2013 at 2:55

• Changed state: Closed