Well, I did not rename RequestProcessor (at least not in events sequence) on purpose, it is the result of recent email exchanges we had (implicitly "gained"). 

The decision to _remove/break_ RequestProcessor happened today morning (my time), but before that decision, I had introduced RequestProcessor2 (initially very badly named, on Wed I renamed it to RequestStrategy) in parallel with keeping but deprecating ReqProcs.

As there was multiple problems with RP interface (badly named methods, inconsistent method signatures and such), but also how they got registered and unregistered to repository (was not thread safe and too error prone), I decided to introduce a "clean slate" _new_ RequestProcessor2 (again, later renamed to Strategy), while keeping backward compat (again, all this happened earlier this week, way before the email for 1/2/3 options was fired on list).

Now, that I applied the option 3, and removed RequestProcessors and support for backward compat, I can rename the RequestStrategy back to RequestProcessor if we see that change as really needed... I did not see it important. Either way, we broke backward compat.