[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsia] [wsrp-interfaces] redirectURL field as a polite method
I think the use case for this is when the URL (or possibly even the need
for a redirect) that is the target of the redirect is not known until the
logic of the action executes. Having this available does not replace the
ability of the markup to contain direct links, it suppliments it with
functionality equivalent to what http offers (and web application
developers often exploit) today.
Gil Tayar
<Gil.Tayar@webcol To: wsia@lists.oasis-open.org, wsrp-interfaces@lists.oasis-open.org
lage.com> cc:
Subject: RE: [wsia] [wsrp-interfaces] redirectURL field as a polite
08/08/2002 12:56 method
AM
Rich,Yossi,
Your original question had an important sub-question in it: "Are there use
cases that would not be covered by
the link the user clicked directly going to the new URL?". To my thinking,
no, except for the fact that the redirectURL is politely asking the
Consumer
to do it, while the other option is forcing the user to go there without
the
consensus of the Consumer.
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Tue, August 06, 2002 16:22
To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
Subject: RE: [wsia] [wsrp-interfaces] redirectURL field in
InteractionResp onse data structure
Well, for me redirect means to change the target URL, but not the handling
of the URL.
Users don't usually receive URLs (exception = address bar of HTML
browsers), but rather view the contents the URL refers to. It may be a
nit, but I've stumbled over it in the past explaining systems to new users
....
"Tamari, Yossi"
<yossi.tamari@sap To:
wsia@lists.oasis-open.org, wsrp-interfaces@lists.oasis-open.org
.com> cc:
Subject: RE: [wsia]
[wsrp-interfaces] redirectURL field in
08/06/2002 09:03 InteractionResp onse
data structure
AM
Hi Rich,
If you don't like the semantics of "send" then you must also not like the
semantics of "redirect", right?
Yossi.
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Tuesday, August 06, 2002 3:54 PM
To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
Subject: RE: [wsia] [wsrp-interfaces] redirectURL field in
InteractionResp onse data structure
Good points.
I'm not sure "send" has the right semantics though as the _user_ isn't
really sent the URL. How about "the entity would like the user to view a
different URL"? This carries the semantics of viewing the contents of the
URL rather than the URL itself, but separates from the question of what
does it mean to view this particular form of URL.
"Tamari, Yossi"
<yossi.tamari@sap To:
wsia@lists.oasis-open.org, wsrp-interfaces@lists.oasis-open.org
.com> cc:
Subject: RE: [wsia]
[wsrp-interfaces] redirectURL field in
08/06/2002 08:31 InteractionResp onse
data structure
AM
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>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC