RE: [wsrp-wsia] [change request #165] Semantics of no userProfile vsno userProfile data

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

This change request raises two questions for me:
1. Is there a requirement that the sharing of a Portlet across a group of 
users be communicated to it? My first take is "no". There may be an 
efficiency that can be gained, but I don't see how it is a requirement.

2. If such a requirement exists, how tight should the semantics for the 
Consumer be?

Rich Thompson




Andre Kramer <andre.kramer@eu.citrix.com>
02/21/2003 04:28 AM
 
        To:     wsrp-wsia@lists.oasis-open.org
        cc: 
        Subject:        RE: [wsrp-wsia] [change request #165] Semantics of 
no userProfile  vs no userProfile data


UserContext is already a bit more general than you suggest, as it carries
the userContextKey and userCategories which I believe are valid on a user
group basis. Separating this sharing status out means that UserContext is
not as self contained a s it could be.

regards,
Andre

-----Original Message-----
From: Michael Freedman [mailto:Michael.Freedman@oracle.com]
Sent: 20 February 2003 21:54
To: wsrp-wsia@lists.oasis-open.org
Subject: Re: [wsrp-wsia] [change request #165] Semantics of no
userProfile vs no userProfile data


I don't think this information should be carried in the UserContext as 
what we are trying to communicate is whether this portlet contains 
customizations that are user specific or not.  This information should 
either be passed as part of the PortletContext or conveyed when a clone 
occurs [forcing the producer/portlet to remember the details if it cares].
      -Mike-


Rich Thompson wrote:

>Document: Spec
>Section: 6.1.19 UserContext Type
>Page/Line: 39/22
>Requested by: Andre Kramer
>
>Old text: [insert]
>Proposed text: A Consumer that is sharing a Portlet among users MUST NOT 
>supply a value for the userProfile field. A Consumer that is not sharing 
a 
>Portlet MAY omit all userProfile fields if no user information is 
>available or requested but MUST supply a userProfile field.
>
>Reasoning:
>A producer MAY then use the fact that UserProfile is or is not nil, for 
>example,  in deciding whether content rendered is cacheable for the given 

>user context (i.e. the perUser scope can then be for a particular end 
user 
>or a group of users identified by a UserContextKey) or for all users 
>(other userContextKeys then the one that content was rendered for).
>
>Better than an extra boolean: UserContext.isSharedContext?
>
>[need to then make the element nillable in wsdl or add a boolean element]
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>
> 
>



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>