Re: [wsrp-interop] wsrp-extension value encoding clarification

well, I'd say correct.

Any form of double encoding is needed
here.

The spec only mentions that extension
params become the value of a param (which has to be URL safe) and says
that there can be muliple params which are then encoded using query-like
syntax.

This effectively means that the chars
"&" and "=" need to be escaped by whatever codec.

Since these are part of an extension,
the extension could declare/specify the encoding here.

But I think going with double URL escaping
seems fine to me.

Mit freundlichen Grüßen / Kind
regards

 
 
 
 

Richard Jacob

 

Team Lead Portal
Standards & WCM development

WSRP Standardization Lead

IBM Software Group,
WPLC

WSS Websphere Portal
Foundation Development 1

Phone:
+49-7031-16-3469
 IBM Deutschland Research
& Development

E-Mail:

 Schoenaicher Str. 220

 
 
 71032 Boeblingen

 
 
 Germany

IBM Deutschland Research
& Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter

Geschäftsführung: Dirk Wittkopp 

Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
HRB 243294 
 

 

From:
Nathan Lipke <>

To:


Cc:
Andrew Wright <>

Date:
12/08/2009 10:45 PM

Subject:
[wsrp-interop] wsrp-extension value
encoding clarification

I was reading the wsrp-extensions part of the spec: 9.2.1.9
and I am assuming parameter names and values should be encoded.

Here's the relevant section:

9.2.1.9 wsrp-extensions

Extensions to the data supplied on the URL
which this protocol defines MUST use the following sequence to encode the
additional information into the wsrp-extensions
portlet URL parameter:

1.        A
querystring-like [20]
value is built from the parameter identifiers and values to be set. Parameters
that are an array of strings can be specified by repeating the parameter.
For example, if a Portlet has two additional parameters, one is an array
of strings (parameter name is "param1") and and the other a simple
string (parameter name is "param2"), results in;

"param1=value1&param1=value2&param2=value3

2.        The
string built in step #1 is url-encoded so that it can appear as a querystring
value or part of the path portion of the URL. The example becomes;

param1%3Dvalue1%26param1%3Dvalue2%26param2%3Dvalue3

3.        The
url-encoded string is then used as the value of the wsrp-extensions
portlet url parameter or to replace it within a template.

So for example if param1=value1 were more
complex:

Replace "param2" with "param=2"

Replace "value3" with "this
& that"I would expect the
resulting string to be:

param1%3Dvalue1%26param1%3Dvalue2%26param%253D2%26%3Dthis%2520%2526%2520that

Is this correct?

Thanks,

Nate