RE: [wsia] [wsrp-interfaces] redirectURL field in InteractionResp onsedata structure

["Tamari, Yossi" <yossi.tamari@sap.com>]

Hi Rich,

I would say "the entity would like to _send_ the user a different URL" since the URL may point to a zip file for downloading for example.
I agree that we should not define how the portal handles this URL, though I do think there are use cases for displaying the result in place of the current content (for example this is a URL that builds a map image to display instead of the portlet's content).

	Yossi.

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Tuesday, August 06, 2002 3:20 PM
To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
Subject: [wsia] [wsrp-interfaces] redirectURL field in
InteractionResponse data structure



Lines 30-34 of page 36 in the v0.3 draft spec ask what will be the
semantics of this field (introduced from the JSR168 interface). I would
suggest that the semantics be "the entity would like to show the user a
different URL". It would then be up to the Consumer whether this replaces
the current page or launches a new one (choice likely depends on the
browser in use, etc). Replacing the entity's portion of the page would seem
to be a weird thing to suggest as the URL is not likely a WSIA/WSRP entity.
If it were an entity, a single URL is not enough with the current design.

Are there use cases driving the insertion of this into the JSR168 interface
that this would not cover? Are there use cases that would not be covered by
the link the user clicked directly going to the new URL?



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>