Re: [wsrp] suggested 1.0 errata

[Rich Thompson <richt2@us.ibm.com>]

I think this would have performance
implications for the normal case and unexpected side-effects in the direct
access case.

Normal case:
 - Since the Producer would not
know how the Consumer indicates to itself the need to rewrite a resource,
the Consumer would have to presume that all resources need to be rewritten
(could exclude some based on mime types ... what would it mean to rewrite
a gif?) with the resulting performance impact.

Direct access: 
 - If the Consumer sends a resourceTemplate
of {wsrp-url} and the Producer actually needs the resource rewritten (e.g.
a JavaScript file), then the Producer is forced to fall back to using the
Consumer URL rewriting expression and requiring the Consumer rewrite the
markup fragment as well. This would not be expected by developers.  

On the value side, how would the Consumer
be able to determine that the browser is able to access all resources the
Consumer could be directed to?

Rich Thompson

Andre Kramer <andre.kramer@eu.citrix.com> 06/25/2003 11:43 AM

To:        wsrp@lists.oasis-open.org         cc:                 Subject:        [wsrp] suggested 1.0 errata

Section 10.2.2.5        resourceTemplate

Both wsrp-url and wsrp-requiresRewrite are currently required in resource templates.
Could we make {wsrp-requiresRewrite} optional?
This would prevent a Producer indicating if a consumer rewrite is required, but:

        -- Consumers can choose to be conservative and always re-write.
       -- can also allow the consumer to decide whether or not to re-write (based on resource MIME type or file extension).

        -- can be used to conditionally proxy resources:
               if the consumer decides that browsers can directly access resources,
               it can send templates with just "{wsrp-url}" as the value for renderTemplate and secureRenderTemplate.
               The effect would be for producers/portlets to directly write-through resource urls into the mark-up.

I believe the ability to pass through resource urls into mark-up,
using "{wsrp-url}" as the (secure)resource template value,
allowing browsers to directly fetch images etc, will be valuable in 1.0.

regards,
Andre