[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsrp-wsia] [change request #208] Conformance test requires cyclingConsumer?
Document: Spec Section: 6.1.3 Page/Line: 27/15-19 Requested by: Rich Thompson Old text: If the portletState field has a value, the Consumer MUST return this value on subsequent calls using the same portletHandle. Note that such uses MAY span multiple starting and stopping cycles of the Consumer and therefore this state MUST be persisted by the Consumer until successfully invoking destroyPortlets() with the related portletHandle. New text: If the portletState field has a value, the Consumer MUST return this value on subsequent calls using the same portletHandle. Note that such uses can span multiple starting and stopping cycles of the Consumer and therefore this state MUST be persisted by the Consumer until successfully invoking destroyPortlets() with the related portletHandle. Reasoning: The way this is currently worded our conformance test would require cycling the Consumer (would that be a power cycle or a reboot?). Do we really want to do that test? This change would eliminate the requirement on our testing. ---------------------------------------------------------------- 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] | [List Home]