[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?
yes, currently we only defined a "passive" producer, i.e. the consumer has
to poll periodically.
Alejandro's suggestion is more a kind of optimization like the DNS serial
number. The consumer has to poll here anyway.
Here we would need to deal with things like epoches, expiration etc.
Therfor I wouldn't add it so late in the game.
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
|---------+---------------------------->
| | Rich |
| | Thompson/Watson/I|
| | BM@IBMUS |
| | |
| | 06/16/2003 06:45 |
| | PM |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: wsrp@lists.oasis-open.org |
| cc: |
| Subject: Re: [wsrp] service & portlet descriptor changes, how does a consumer know? |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
I think any v1 solution is going to be dependent on the Consumer
periodically polling for new metadata and therefore not be a satisfying
solution. As we tackle the coordination issues, perhaps this could be a
subtopic as a metadata update is ideally something the Producer proactively
tells the Consumer.
Rich Thompson
Alejandro Abdelnur
<Alejandro.Abdelnur@Sun.COM> To: WSRP OASIS
<wsrp@lists.oasis-open.org>
Sent by: cc:
Alejandro.Abdelnur@Sun.COM Subject: Re: [wsrp] service
& portlet descriptor changes, how does a
consumer know?
06/16/2003 12:24 PM
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]