OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interfaces message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wsrp-interfaces] Q: cloned portlet handle scope

I think the key here is that the Consumer is free to make this choice as appropriate for the situation. It decides which portletHandle is used for which users and also indicates to the Producer/portlet whether or not additional state changes are permitted without producing a further clone. It is much more likely that the customized portlet will be used for all users if the current user is a page designer using tools provided by the Consumer for that purpose. On the other hand, I would expect that most of the time when "normal end-user" interactions with a shared portlet (POP or not) result in a clone, the newly cloned portlet would be considered unique to the user.


"Klein, Avi" <avi.klein@sap.com>

10/14/2004 04:13 AM

[wsrp-interfaces] Q: cloned portlet handle scope

Hi All,

I wonder how your implementation deals with the following scenario:

Consumer C uses a POP of Producer P.

User A (in the consumer) clicks a button in the portlet which results in a PBIA, the portletStateChange = cloneBeforeWrite since this is a POP.

The new portletHandle is returned to the consumer.

Do you scope this handle to specific User A or does this new handle is now shared by all users that might try to use this portlet.

In other words, does the cloning action in this case is intended for enabling the state change of that POP in the producer (and the producer is then managing the personalization for any of users within that new handle scope) or should each user first action result in a cloneBeforeWrite of its own.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]