RE: [wsrp] getResource and transport headers

["Spector, Artem" <artem.spector@sap.com>]

Since resources are treated in same manner as markup (MarkupParams ->
MarkupResponse), we could use the existing markup cache control
mechanism for resources, and not to relay on transport protocol.

Let's consider a situation when the getResource() implementation
downloads the requested resource from a web server via HTTP. In that
case it could add an If-Modified-Since header to the http request based
on the validateTag of MarkupParams. The http response status (304) and
the Cache-Control header returned by the web server can be translated to
the CacheControl structure of the MarkupContext.

Regards,
Artem

-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com] 
Sent: Wednesday, April 27, 2005 10:23 PM
To: wsrp
Subject: [wsrp] getResource and transport headers

The current spec of getResource does not seem to consider the issue of 
any transport headers associated with the resources. The primary use 
case is to return HTTP caching headers for the resource.

I see two possibilities:

a. Let the Producer return such headers along the transport, and include

language on how Consumers should do treat those headers.
b. Or let the Producer return mimeHeaders along with the response.

Any comments?

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