[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-wsia] Re: [change request #177] Templates MUST send placeholders
I would say that this doesn't concern the default template (therefor I
didn't add section 10.2.2.9 in the request).
Here a MUST might not apply for the reasons you stated. Second there might
be an action template which overides the default template for example and
has the placeholders (because of the MUST) in it.
However, we need to clarify the behaviour if default templates are used.
Mit freundlichen Gruessen / best regards,
Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com
|---------+---------------------------->
| | Andre Kramer |
| | <andre.kramer@eu.|
| | citrix.com> |
| | |
| | 02/26/2003 05:36 |
| | PM |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: wsrp-wsia@lists.oasis-open.org |
| cc: |
| Subject: RE: [wsrp-wsia] Re: [change request #177] Templates MUST send pla ceholders |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
We should discuss how this affects the default templates. Must they
include,
e.g. {wsrp-interactionState} which is only defined for actions? Should
producers edit out {wsrp-*}s that do not apply to the specific type of
template when they use a default template?
regards,
Andre
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 25 February 2003 16:55
To: wsrp-wsia@lists.oasis-open.org
Subject: RE: [wsrp-wsia] Re: [change request #177] Templates MUST send
pla ceholders
I would see this as assisting the portlet developer as it can then be
assumed that requests for these items is always valid. The Consumer might
reject all attempts to change the mode, for example, but it seems more
appropriate for the Consumer to implement this rather than requiring all
Portlet developers to check whether they can write the request to the URL.
Rich Thompson
Eilon Reshef <Eilon.Reshef@webcollage.com>
02/25/2003 11:17 AM
To: wsrp-wsia@lists.oasis-open.org
cc:
Subject: RE: [wsrp-wsia] Re: [change request #177]
Templates MUST send pla ceholders
Does it help if the portlet developer can assume that it those parameters
are ALWAYS set, or is it because we want to force Consumers to act
"correctly"?
If it's the first, I see value in enforcing MUST versus SHOULD. Otherwise,
it seems more of a "best practice" statement: in reality we can't enforce
correct behavior anyway (e.g., the Consumer receives the values from the
portlet, but and ignores them...), so forcing the Consumer to *send* the
template is only part of the equation.
I also see some value in allowing Consumers to ignore windowState changes
(e.g., a Consumer that does not allow change of window state maybe because
it's a public Web site and/or it has prior knowledge about the portlet).
Possibly also of the others (e.g., Consumers that want to prohibit
navigation for some reason and always pass e.g., "#" as a URL).
I think the question is whether this helps the portlet developer to limit
the matrix of options in a MUST sort of way.
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Tuesday, February 25, 2003 18:00
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] Re: [change request #177] Templates MUST send
placeholders
Document: Spec
Section: 10.2.2.1 - 10.2.2.8
Page/Line: 61/xx
Requested by: Richard Jacob
Old text: The Consumer SHOULD integrate placeholders for at least the
portlet URL parameters wsrp-navigationalState, wsrp-interactionState,
wsrp-mode and wsrp-windowState in its template.
New text: The Consumer MUST integrate placeholders for the portlet URL
parameters wsrp-navigationalState, wsrp-interactionState, wsrp-mode and
wsrp-windowState in its template. The Consumer SHOULD integrate
placeholders for the other portlet URL paramters defined in this
specification.
...
Analogues for the other templates: change SHOULD to MUST and add SHOULD
for other URL parameters not mentioned.
Reasoning:
If the Consumer chooses not to pass these placeholders within its
templates the portlet can not work if it requires them.
The portlet can still choose not to use the placeholders and the Consumer
can handle this appropriatly.
----------------------------------------------------------------
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