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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

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


Subject: Re: [wsrp] RuntimeContext.portletInstanceKey uniqueness requirement



I think namespacePrefix is optional for the same reasons templates are optional. It is required when a Portlet indicates it does URL template processing.

Rich Thompson



Alejandro Abdelnur <Alejandro.Abdelnur@Sun.COM>

05/20/2003 11:57 AM

       
        To:        Rich Thompson/Watson/IBM@IBMUS
        cc:        Alejandro Abdelnur <Alejandro.Abdelnur@Sun.COM>, WSRP OASIS <wsrp@lists.oasis-open.org>
        Subject:        Re: [wsrp] RuntimeContext.portletInstanceKey uniqueness requirement



But they are both optional. Shouldn't be namespacePrefix mandatory, if  
not I don't see much of a use of having 2 optional things for the same  
purpose.

Alejandro


On Tuesday, May 20, 2003, at 06:30 AM, Rich Thompson wrote:

>
> I would say that there is no overlap between portletInstanceKey and  
> portletHandle. I understand these as:
>
> portletHandle: Producer defined means of identifying a particular  
> configured portlet.
>
> portletInstanceKey: Consumer reference to a use of a portletHandle.  
> Uniqueness is required at registration level. These may come and go in  
> a manner that appears random to the Producer as portlets are added to  
> and/or removed from pages.
>
> namespacePrefix: Consumer supplied token which is unique for this  
> portlet instance on the page currently being aggregated. This token is  
> allowed to change on the next call requesting markup though it likely  
> won't as that would make Consumer caching less efficient ....
>
> There is some overlap between namespacePrefix and portletInstanceKey.  
> We kept the namespacePrefix only because we do not expect all classes  
> of Consumers to have something to supply as a portletInstanceKey, but  
> all Consumers can generate something for namespacePrefix.
>
> Rich Thompson
>
>
<image.tiff>
>
>
>
>
>
> I'm a little bit confused with the requirement of portletInstanceKey to
> be unique within the RegistrationContext. It's kind of a second unique
> key, being the first one the portletHandle. If the purpose is to
> namespace multiple occurrences of the same portlet in the consumer the
> namespacePrefix should be enough? Or if we want to free the consumer
> from this burden, why do we need the portletHandle then, for the
> consumer the portletInstanceKey would be enough?
>
> What am I missing here?
>
> I should keep re-reading the spec every day not to forget things. I'm
> under the impression that we are describing each thing well but we do
> not do a very good job at indicating their contextual purpose.
>
> Thanks
>
> 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
>
>



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