Mike Heath wrote:
What the FAQ is saying is that the idle event wont tell you which request message was issued when the timeout occured. So using an idle read to detect an unresponsive connection is perfectly legitimate. I don't see why using idle wouldn't work for pipelining. If the session times out, it gets closed which would cause any pending requests to fail anyway. I may just be presumptuous. Am I missing something?
This is pipelining...using a single connection for reuse for multiple requests, which tells me that a sessionIdle would probably not work.
But if you are saying its possible, then great! Jeff
-Mike
