Re: [wsrp] Dynamic wiring of transient properties and navigationalparameters

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

We use three different strengths of
language to describe Consumer distribution of the three coordination types:
 - Events: Completely optional
- Consumer is free to ignore both known and unknown events
 - navParms: Consumer encouraged
to cause sharing of items with same QName from different POPs (i.e. SHOULD).

 - transientProperties: No explicit
language, but the implication is that properties with the same QName are
shared

I could see how a case could be made
for updating a transientProperty's value, provided some Portlet has already
initialized that property. 

I would want a stronger reason why we
would require the Consumer to automatically create new shared properties
at runtime as this might be expensive for some Consumer implementations.


I also wonder what kind of semantics
we would even suggest for an unexpected navParm appearing in an update
(same as we have for events??).

Rich

Subbu Allamaraju <subbu@bea.com>

02/06/06 12:30 PM

To	OASIS WSRP TC <wsrp@lists.oasis-open.org>
cc
Subject	Re: [wsrp] Dynamic wiring of transient properties and navigational parameters

Stefan Hepper wrote:
> Hi Subbu,
> do you have a use case for this? And how about the URL? Can the URL
have 
> new nav params?

I don't have a particular use case. Just like events, a portlet should
be able to return new properties that will then be sent by the consumer
to portlets that require those properties. I agree that to receive these
properties, a portlet must specify those in its description.

> 
> I think this would make the consumer logic quite complex.

Not sure how returning an unadvertised value would make the consumer 
more complex?

In any case, we need to clarify the behavior in the spec.

Subbu

> 
> Stefan
> 
> Subbu Allamaraju wrote:
>> For events, the spec supports dynamic wiring by making raised
event 
>> description optional in PortletDescription.
>>
>> For transient properties and navigational parameters, it is not
clear 
>> to me if a portlet can return updates for properties that it did
not 
>> declare in its PortletDescription.
>>
>> Particulary, can the fields navigationParameterUpdates and 
>> transientPropertyUpdates in UpdateResponse contain properties
not 
>> described in the portlet's description?
>>
>> Subbu
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC
that
>> generates this mail.  You may a link to this group and all
your TCs in 
>> OASIS
>> at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
> 
> 


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php