[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp] service & portlet descriptor changes, how does a consumer know?
We discussed the particular issue of the PortletDescription before and I believe the solution to be that portlet descriptions are very much immutable once advertised (this constant ness applies to clones too, as they inherit meta data).
I suspect anything that varies should be exposed as portlet properties and public offered portlets (pos) just come and go. Similarly for the service description, a new producer may need to be created if anything other than the list of pops requires changing.
regards,
Andre
-----Original Message-----
From: Alejandro Abdelnur [mailto:Alejandro.Abdelnur@Sun.COM]
Sent: 16 June 2003 17:24
To: WSRP OASIS
Subject: Re: [wsrp] service & portlet descriptor changes, how does a
consumer know?
It's somehow related, it's a lack of communication issue. But we are
not changing the interface, we are not changing the behavior. It's just
a call returning different data.
The problem is, the caller (consumer) has no easy way to find out if
data has changed or what has changed. And, in WSRP the rest of the
operations heavily depend on the information returned in the
ServiceDescription and PortletDescription structures.
How does a producer let the consumers know? Are we expecting consumers
to fetch the descriptions and do a diff with the previously fetched
descriptions?
Alejandro
On Monday, June 16, 2003, at 09:05 AM, Subbu Allamaraju wrote:
> Alejandro,
>
> Just curious - how this scenario different from some RPC service
> changing its interface or changing its behavior without letting its
> clients know?
>
> Subbu
>
> Alejandro Abdelnur wrote:
>> How does a consumer detect that the descriptor of a service or a
>> portlet has changed?
>> As the spec is today, it seems that consumer should keep a copy and
>> do a comparison with the producer descriptor to find out.
>> Wouldn't make the life of consumers easier if we have a sequence
>> number in the descriptor? This would allow consumers to check and
>> quickly decide if it has to update things.
>> Alejandro
>> You may leave a Technical Committee at any time by visiting
>> http://www.oasis-open.org/apps/org/workgroup/wsrp/members/
>> leave_workgroup.php
>
>
>
> You may leave a Technical Committee at any time by visiting
> http://www.oasis-open.org/apps/org/workgroup/wsrp/members/
> leave_workgroup.php
>
You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wsrp/members/leave_workgroup.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]