[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp] Setting SessionContext.expires to zero
I agree with you on caching. My question is regarding session and I’m probably beating a dead horse. I just wanted to know if returning a session having a session expires of 0 had special meaning to the consumer. I want to be clear on what options are possible if the producer has determined that the session has expired and the implications:
1) Return the same session id with expires of zero – consumer does not use session in future calls
2) Return a new session id with > zero expires – the normal case (I presume)
3) Throw invalid session fault – causes consumer to repeat last WSRP operation without a session id. I believe this is to force re-passing of templates once more if previously stated they were stored in session, etc.
Hopefully, these options for returning session and the implications are correct.
From: Michael Freedman [mailto:firstname.lastname@example.org]
As further information, 0 is commonly the setting when
one only wants validation level caching (checks). I.e. return a 0 expires
and an validation tag.