RE: [wsrp-interfaces] Fw: [wsrp] Additional use cases for issue #44 (set new public params)

Do you expect end users to edit URLs to
override consumer (PP) settings? Then I would ask (to prime the call today):

 

-         
Is such editing
of URLs desirable? Allowed for Web experts for simple URLs, I agree, but for
Portlets?

-         
Are URLs
not too obfuscated (encoded) to allow manual editing? Because of size
limitations, the URL may be by-reference.

-         
Why need
the consumer be involved? Since user explicitly submits she may not expect the
consumer Portal to be in the loop.

-         
Are
other types of URLs (to resources and out-of-Portlet Web content) also not to
be covered?

-         
Why
overload PPs with this feature? Maybe a separate user to portlet channel would
be better? Something more like a query string?

 

My suggestion for 3.0 would be to look at
having a trailing URL part (wsrp-portlet-query-string) that can be added to consumer
produced URLs that is forwarded unmodified (or as a separate key/value list) by
the consumer to explicitly model query strings if we really require and can
support such a feature.

 

Regards,

Andre

 

From: Rich Thompson
[mailto:] 

Sent: 27 July 2005 19:18

To:


Subject: Re: [wsrp-interfaces] Fw:
[wsrp] Additional use cases for issue #44 (set new public params)

 

To say this another way, PPs enable user/Consumer driven coordination. The
current question is whether to allow Portlets to generate URLs that enable the
user driven portion of this rather than requiring such URLs be generated by the
Consumer. I think the use cases Stefan posted say there is value to allowing
Portlets to generate such URLs. 

Rich