Perhaps one solution to this is for the
response to include a Vary=Configuration-Context header so that different
configuration contexts do not use a previously cached response. If so,
this might be worth mentioning in the Config Mgmt spec.
Best regards,
David.
From:
"Sarabura, Martin"
<>
To:
"OSLC CCM TC ()"
<>
Date:
2016-05-10 23:16
Subject:
[oslc-ccm] Caching
versioned resource when passing config context in header
Sent by:
<>
Nick et al., I want to make sure I understand
this...
https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/config-mgt/config-resources.html#configcontext
If the server accepts a configuration context
in the header of the request, does that mean you've broken caching? Two
different requests may ask for the same resource, each with a different
header context, yielding a different resource.
Also, does the spec provide a method for
the client to discover which approach the service supports?
Thanks,
Dr. Martin Sarabura
R&D Fellow, PTC
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
