Re: [wsrp] RuntimeContext.portletInstanceKey uniqueness requirement

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

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

Alejandro Abdelnur <Alejandro.Abdelnur@Sun.COM> 05/20/2003 09:00 AM

To:        WSRP OASIS <wsrp@lists.oasis-open.org>         cc:                 Subject:        [wsrp] RuntimeContext.portletInstanceKey uniqueness requirement

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