Re: [wsrp-conformance] AS071/CS074 clarification

[Subbu Allamaraju <subbu@bea.com>]

I agree.

However, to avoid impersonation of these parameters, I also suggest a 
rewording of AS071 to include only those parameters that the consumer 
included in the templates. So, if a consumer chose not to include 
wsrp-portletHandle in the template, the consumer do not have look for 
this handle in the request.

Subbu

Rich Thompson said the following on 03/08/2004 07:54 AM:
> 
> It seems like the key issue here is that CS157 doesn't have a 
> corresponding assertion; namely:
> If the Consumer includes wsrp-portletHandle, wsrp-userContextKey, 
> wsrp-portletInstanceKey or wsrp-sessionID in a template, Producer 
> written URLs based on that template MUST replace the specified portlet 
> URL parameter with the value the Consumer separately supplied in a data 
> field
> 
> I think it is important that the data is able to make a full round-trip 
> from one Consumer invocation to the next ...
> 
> Rich
> 
> 
> *Subbu Allamaraju <subbu@bea.com>*
> 
> 03/05/2004 03:38 PM
> 
> 	
> To
> 	wsrp-conformance@lists.oasis-open.org
> cc
> 	
> Subject
> 	[wsrp-conformance] AS071/CS074 clarification
> 
> 
> 	
> 
> 
> 
> 
> 
> I am looking for some clarification on how AS071 interprets CS074.
> 
> AS071 requires that the consumer propagate various URL parameters to the
> producer. I have trouble with the following parameters and would like to
> understand how others interpret these statements.
> 
> wsrp-portletHandle
> wsrp-userContextKey
> wsrp-portletInstanceKey
> wsrp-sessionID
> wsrp-navigationalState
> 
> It is possible that the producer-inserted values for these parameters in
> URLs may be different from the values known/communicated in the protocol.
> 
> For example, the portletHandle returned by implicit/explicit cloning may
> be different from the value the producer inserted in URLs. This may not
> happen in practice, but there is room for error.
> 
> Thanks for any clarification.
> 
> Regards,
> 
> Subbu
> 
> To unsubscribe from this mailing list (and be removed from the roster of 
> the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/wsrp-conformance/members/leave_workgroup.php.
> 
>