getResource and transport headers

[Subbu Allamaraju <subbu@bea.com>]

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