Originally posted by chandana sapparapu:
The following spec is clear for me.
My question is does a scenario arise often in practice? And if so, could you let me know when.
Thanks.
Well, my understanding is that spec describes this point to warn developers not to keep references to the request/response objects in different request handling threads. If you want to try this, then imagine someone saving a reference to the request/response object in the session object, and then trying to access the these objects in different requests handling threads. I am not sure what the behaviour will be as I have not tried this before. But the results will definitely be not as expected.
I guess other javaranchers may explain this in a better way.
Thanks
Tejas