Re: 1.1m4 release notes --- Added a static “current” property to...

[Patrick Logan]

Thanks for the explanations. We had a situation where a Resource was
inadvertently wired in using Spring's default "singleton" scope. Fortunately
under high load we did see concurrency conflicts show up when setting Status.
The easy fix was using the static thread-local accessor, but the true fix was
creating the Resource per request. I wanted to make sure I fully understood
getResponse() before putting it back in our code.