I think it is dangerous to suggest an
http proxy request for a resource that specified using getResource is likely
(or expected) to work. The references to state, etc for handling the call
are totally different. Even if the Producer provides a proxy facility for
its portlet's resources, how is the Consumer to know the correct url (either
base or format of a reference or querystring)?
Rich
Andre Kramer <>
12/22/2004 10:24 AM
To
"'Michael Freedman'"
<>,
cc
Subject
RE: [wsrp] Issue #29: Is
metadata needed to indicate support forg etResource?
forgetResource (subject)? Forward
or backwards interop can be by degrading the HTML or falling back to HTTP
but I would encourage 2.0 (consumer) implementations to support getResource
and 2.0 producers to also provide a 1.0 service.
Regards,
Andre
From: Michael Freedman [mailto:]
Sent: 21 December 2004 17:55
To:
Subject: Re: [wsrp] Issue #29: Is metadata needed to indicate support
forgetResource?
And vice-versa: so a producer
can adapt to run in a 1.0 consumer.
Rich Thompson wrote:
Issue # 29
Spec section:
SubCommittee: Interfaces
Owner: Andre
Description: Isn't
metadata needed to tell a Consumer whether or not a Producer supports getResource
(or is it always supported if urls encode for it and Consumers never invoke
it unless a url has encoded wsrp-useOperation=true)?
