On 2. If a session has a user specified timeout, the container should not start a new session after timeout.
-----Original Message----- From: Raymond Feng <[email protected]> Sent: Wednesday, February 17, 2010 4:10 PM To: [email protected] Subject: Re: Travelsample Hi, I can reproduce the problem now. It leads to two questions: 1) Do we model the conversation correctly here for the search? Do we use the conversation to correlate the request and response for the asynchronous search? 2) What's the correct behavior if the conversation expires? Should the container start a new conversation instead of complaining about the expiration? Thanks, Raymond From: Albert Tsang Sent: Wednesday, February 17, 2010 10:10 AM To: [email protected] Subject: Re: Travelsample Thanks Raymond, fyi you must execute a search, let some time pass, reload or refresh the page and then re-run [The entire original message is not included]
