Rethink second result boolean method calls

[crhntr]

The behavior of the handler when the receiver returns a false boolean for the second result, was based on methods being able to receive and write to the HTTP Response Writer.

This is still acceptable but not an ideal pattern.

Consider removing support for boolean second value returns.

If you keep it, write a decision record and clearly express the design ideas behind why it should be kept and document some use cases (in examples).

[crhntr]

I fixed the docs to match existing behavior. This is an odd case but users would likely be better served by hand rolled http.Handler implementations.