A modern programming language that makes developers happier.

kotlinlang

<@U8CB137Q8> I've taken a look and have been playing with the code. It's a good start - however to me it feels like the various Filters should be separate, ie. Total request counting, Path request counting, Path request timing, and the users can add them as required (or we can create composed filters that do the lot). Also, at the moment I'm pretty sure that if you add a Filter twice, eg. a counter AND a timer, you'll end up with double request counting for "all requests" - however I can't prove that yet!  Splitting things out would solve that problem, and I think it might end up with the code being simpler. Maybe start with all 3 Filters being totally separate and then try to tease out the commonality that way? There might be a use-case that I'm missing (with the override aspect) though - I'm not sure if the header manipulation is required at all.