Public review comments: Caching of resources - clarification needed

In WSRP 2.0, it is not clear how a producer/consumer would manage 
caching of resources such that intermediate entities such as caching 
proxies, and also user agents can participate in HTTP 1.1 style of caching.

With the WSRP 1.0 style, the resource originator could set caching 
headers like Etag, and Last-Modified. Intermediaries/user agents could 
then cache resources by following these headers, and also supplying 
If-Modified-Since/If-Not-Modified-Since and Etag headers.

How do these headers map to the input/output of the getResource 
operation? I can see that the Etag header could be mapped to 
validateTag, but what about other caching headers? Who is responsible 
for generating these headers and how do these headers map to WSRP 2.0?

Subbu
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.