RE: [wsrp] suggested 1.0 errata / direct resources

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

Hi Andre,

 

Such resources also cannot count on using cookies, sessions etc., right? 

The producer will also be taking the chance that the end user has no internet access to the direct URL (because of firewall issues, for example), and therefore the portlet can break, without either the consumer or the producer being able to fix this, right? Or is the consumer allowed to decide to proxy the resource anyway?

 

I have a feeling I am still not understanding your expected behavior of producers/consumers in this case...

 

    Yossi.

-----Original Message-----
From: Andre Kramer [mailto:andre.kramer@eu.citrix.com]
Sent: Friday, June 27, 2003 12:18 PM
To: wsrp@lists.oasis-open.org
Subject: RE: [wsrp] suggested 1.0 errata / direct resources

I still see being able to avoid proxying resources as a high priority performance optimization, but maybe my suggestion of just making {wsrp-requiresRewrite} optional was not a great one. Here is a proposal that adds to, rather than tweaks, the spec. It could be a vendor extension, or a 1.1 feature, but I wanted to put it on the table (as developers will just write absolute urls in their fragments otherwise, I fear):

 

 

The proposal, that I have in mind, is to add a new template (10.2.2.X and a field in Templates 6.1.6). Let's call it "resourceNoRewriteTemplate" for now. (Obviously, we should add a secure equivalent and rename for clarity).

 

resourceNoRewriteTemplate has only one allowed URL parameter {wsrp-url} and is used instead of renderTemplate, if present. But it is only used when the resource requires no rewrite by the consumer i.e. when {wsrp-requiresRewrite} would be set to false for renderTemplate usage.

 

For resources that require no rewriting, the producer writes absolute resource URLs into the {wsrp-url} slot in this template (e.g. to make gif go via a http (non WSRP re-writing) proxy server), with one other change from normal resourceTemplate usage:

 

If the resourceNoRewriteTemplate's value is "{wsrp-url}" (i.e. no chars left of { or right of }) the producer must write in the unencoded URL of the resource. Otherwise the producer must first url encode the absolute resource URL (as is the case for renderTemplate now).

 

We could make use of renderNoRewriteTemplate optional for producers so that we are backwards compatible with the 1.0 TC spec.

 

What do people think? We would then be able to avoid proxying images etc or go via non-WSRP http proxies if no re-write is required.

 

regards,

Andre