“Consumers MUST process and resupply such cookies, as per Section
3.11, in further requests which logically follow and are not concurrent with the
cookie setting reply.”
Which implies the producer must somehow be able to cope with concurrent
requests that carry the stale cookie!
Regards,
Andre
From: Rich Thompson
[mailto:richt2@us.ibm.com]
Sent: 04 May 2005 14:35
To: wsrp
Subject: RE: [wsrp] Action item:
CR313 (cookie advice)
I would rather not introduce a conformance statement in
the fault section that simply says other conformance statements apply. I would
note that the discussion in 3.12 does apply ... Andre, perhaps you could
suggest updated language for that section if you think it is overly
restrictive.
Rich
"Andre Kramer"
<andre.kramer@eu.citrix.com>
05/04/05 03:08 AM
|
To
|
"Subbu Allamaraju"
<subbu@bea.com>, "wsrp" <wsrp@lists.oasis-open.org>
|
cc
|
|
Subject
|
RE: [wsrp] Action item: CR313 (cookie advice)
|
|
I
believe you may still get further requests from the consumer with
stale cookies just after the producer returns
(sets) a new cookie. The
producer can accept these or may fault but it
means that the "MUST"
wording below needs to take into account such
concurrent requests.
I would also like to see this relaxed to allow for
concurrent
(distributed) consumers where returned cookies may
take some time to
propagate before they are available for use on all
future requests.
Regards,
Andre
-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com]
Sent: 04 May 2005 00:24
To: wsrp
Subject: [wsrp] Action item: CR313 (cookie advice)
At the F2F, some people wanted to check if various
proxy/cluster systems
can implement the guidance. Here is the guidance.
"However, since such reprocessing usually
incurs additional processing
and network overhead, Producers are encouraged to
process the request as
usual and return new cookies along with the
response. Consumers MUST
process and resupply such cookies as per Section
3.11."
AFAIK, this guidance is inline with how various
cluster/proxy systems
behave. Depending on how load-balancers are setup,
they eigher create a
new cookie when a request without a cookie is
detected, or modify the
cookie set by a application server node to include
some form of node
identifier.
This is a reminder for folks to check with their
teams.
Regards,
Subbu
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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