[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsia][wsrp-interfaces] newWindowState, newMode, redirectURL
For me this design seems to be too specific. If the porltet decides to
include a URL in its markup that points outside the portal server the whole
browser window should just be redirected (maybe after a message warning the
user). For some pages it might even be illegal to embed them by default.
If the portal wants to include the content of the remote page inside of
itself it should provide the necessary transcoding functionality itself.
Having this as a requirement for the consumer puts a lot of burden on
possible consumers.
Best regards
Carsten Leue
-------
Dr. Carsten Leue
Dept.8288, IBM Laboratory Böblingen , Germany
Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401
|---------+---------------------------->
| | Rich |
| | Thompson/Watson/I|
| | BM@IBMUS |
| | |
| | 07/17/2002 07:31 |
| | PM |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: wsrp-interfaces@lists.oasis-open.org |
| cc: |
| Subject: RE: [wsia][wsrp-interfaces] newWindowState, newMode, redirectURL |
| |
| |
>---------------------------------------------------------------------------------------------------------------------------------------------|
For me this suggests we may want a means by which an entity may hint
whether the new URL should replace its own content, replace the entire
portal page or launch as a new window (does the portal get to tell the
browser to do this?).
"Tamari, Yossi"
<yossi.tamari@sap To: "'Alejandro
Abdelnur'" <alejandro.abdelnur@sun.com>
.com> cc:
wsrp-interfaces@lists.oasis-open.org
Subject: RE:
[wsia][wsrp-interfaces] newWindowState, newMode,
07/17/2002 01:21 redirectURL
PM
That is not how I understood it, and it seems strange: The user has a
(portal) page with a lot of fragments, he clicks on one of these fragments,
and he is sent outside of the portal framework, losing all the other
fragments?
I thought only the specific fragment was replaced by the redirected URL,
and even then it seemed a little "dangerous" in that it breaks the
producer/consumer protocol.
Yossi.
-----Original Message-----
From: Alejandro Abdelnur [mailto:alejandro.abdelnur@sun.com]
Sent: Wednesday, July 17, 2002 6:29 PM
Cc: wsrp-interfaces@lists.oasis-open.org
Subject: Re: [wsia][wsrp-interfaces] newWindowState, newMode,
redirectURL
Yeap, instructs the consumer to send a (HTTP) redirect to the client
with the specified URL.
Gil Tayar wrote:
> Just to be sure - the redirectUrl requests the Consumer to "leak out" of
> itself to another URL?
>
> -----Original Message-----
> From: Rich Thompson [mailto:richt2@us.ibm.com]
> Sent: Mon, July 15, 2002 21:51
> To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
> Subject: [wsia][wsrp-interfaces] newWindowState, newMode, redirectURL
>
>
>
> These were added because Alejandro commented that JSR168 was providing
for
> portlets to include these three items in its response to an invokeAction
()
> call.
>
>
>
>
>
> "Tamari, Yossi"
>
> <yossi.tamari@sap To:
> wsia@lists.oasis-open.org,
> .com>
> wsrp-interfaces@lists.oasis-open.org
> cc:
>
> 07/15/2002 12:47 Subject: RE:
> [wsia][wsrp-interfaces] Refactoring the data objects
> PM
>
>
>
>
>
>
>
>
>
> See my comments marked with [YT].
> (Most of them are in appendix A, since it seems appendix a is the real
> definition of the spec, which I think is wrong, and is a result of what
> Rich mentioned below about the obscurity of the interface.)
>
> The endless debate about putting WSIA concepts in the WSRP standard is
> still there...
>
> Yossi.
>
> -----Original Message-----
> From: Rich Thompson [mailto:richt2@us.ibm.com]
> Sent: Friday, July 12, 2002 9:09 PM
> To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
> Subject: [wsia][wsrp-interfaces] Refactoring the data objects
>
>
> As requested in Tuesday's Joint interfaces call, I have reworked the
draft
> spec in an effort to factor the data items into the scopes presented at
the
> June F2F. Personally I think this obscures too much and that some of the
> data items should move up to first class parameters in the interface.
> Hopefully this version can provide a reasonable basis for a discussion of
> which items should be promoted either for clarity or as part of
supporting
> any factoring of the operations.
>
> Technical note: In order to make this readable but yet leave an
indication
> of what was modified, I accepted the changes and then appended a space on
> the end of changed lines so that a change bar will appear on the left. So
> much changed in Appendix A that it all should be considered modified.
>
> (See attached file: WSIA - WSRP Interface Specification.doc)
>
>
>
>
> #### WSIA - WSRP Interface Specification1.doc has been removed from this
> note on July 15 2002 by Rich Thompson
>
>
>
>
>
> ----------------------------------------------------------------
> 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