I would also note that a separate decision
can be made for each URL concerning whether to use the SOAP operation or
http proxy for serving up the resource. It may be much easier (and reduce
load on the Producer) to serve some URLs using http proxying even while
others require using getResource (need access to the portlet's state).
Rich
"Andre Kramer"
<>
05/27/05 04:56 AM
To
"Subbu Allamaraju"
<>, "wsrp" <>
cc
Subject
RE: [wsrp] getResource question
Yes, URL-addressable resources need their addresses
(URLs) mapped into
the resourceID resourceParam. Remember that these (resourceIDs)
themselves get put on URLs in the markup which is why I though it
clearer as well as more general to not make them explicitly URLs or even
URIs (even though these are likely to be the common cases).
Regards,
Andre
PS. Wish we had WS Addressing endpoint references ...
-----Original Message-----
From: Subbu Allamaraju [mailto:]
Sent: 26 May 2005 22:42
To: wsrp
Subject: [wsrp] getResource question
I've a question on the getResource operation.
AFAIR, the primary use case for this operation was to allow Producers to
serve resources over SOAP instead of HTTP, which was not possible with
WSRP1.0.
But it is not clear how a WSRP2.0 producer can serve URL-addressable
resources via the getResource operation without somehow mapping those
addresses into resourceIDs.
My question is, why is not there a wsrpUrl parameter in the
ResourceParams structure? The lack of such a parameter may impact the
motivation for supporting this operation in producer/consumer
implementations.
Can someone clarify?
Thanks
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
---------------------------------------------------------------------
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
