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.
Nader
From: Michael Freedman [mailto:]
Sent: Tuesday, February 19, 2008
11:22 AM
To:
Subject: Re: [wsrp] Setting
SessionContext.expires to zero
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.
-Mike-
Rich Thompson wrote:
We explicitly chose -1 for never expires such that 0
could have the normal meaning from a caching sense of already expired.
Rich
From:
"Nader
Oteifa" <>
To:
Rich
Thompson/Watson/IBM@IBMUS, <>
Date:
02/14/08 10:35 PM
Subject:
[wsrp] Setting
SessionContext.expires to zero
Rich,
How
should setting SessionContext.expires to zero be interpreted by the consumer:
a) an expired session b) same as unspecified c) other?
Thanks
Nader
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
