David Grudl

To add Mapper means to add two new classes, which will be always autoloaded. Some people scream when you add only one class [that is always autoloaded](https://github.com/nette/safe-stream/commit/313134b8d511469291dd946d5416485b90c159a3#commitcomment-9380744) (even it is...

It this case it would be better to prepare an RFC and open discussion about it and we can implement it in 2.4.

What exactly you mean by "too restrictive"? Yes, it is limited, but extracting it to the new class is not solution - the new DefaultMapper wil be exactly the same...

To change title is probably sufficient, here is history, or not?

https://forum.nette.org/cs/26116-presentermapper-ipresenterformatter-apod

This is of course not intended for „prevent BREACH attack“ just for „complicate“. Subject is incorrect. And I don't like it much, better should be send HTTP header with random...

Better is str_repeat. And length should not be random for the same requests.

Does this feature apply only to Postgresql, or any other databases?

Ještě jiný směr, kam by se to mohlo ubírat: http://forum.nette.org/cs/13458-security-iauthorizator-a-identita#p99180

Exception seems better to me.