90 likes | 117 Views
This proposal aims to introduce a mechanism for sharing reconfigurable portlet state among users in WSRP 1.0, addressing the lack of such a feature. It includes a simple use case for configuring an SMTP server, discusses hierarchy semantics, and considers the usefulness of a Config Portlet Mode. The proposal suggests declaring properties as "Final" and explores the potential for allowing or prohibiting user customization of state. Next steps include answering open questions, finalizing use cases, and beginning feature specification.
E N D
WSRP Interfaces Consumer Defined Portlet Hierarchies
Goals • Introduction of Feature to TC • Gather Feedback To Use Within Subcommittee Discussion
Feature Status • Initial Feature Proposal Draft • Some Subcommittee Email Discussion
Problem Statement • WSRP 1.0 doesn’t provide a mechanism to allow reconfigurable portlet state to be shared amongst users. • Simple Use Case – Configuring SMTP Server for an Email Portlet
General Approach • Introduce CCP Hierarchies
Open Question –What State Can Be Shared? • Portlet Properties • Useful to simplify portlet development • Simple Example – Property to Specify SMTP Server • Opaque Portlet State • Useful when complex UI is necessary • Simple Example – Selecting a Content Folder within the Directory Tree of a Content Repository
Open Question – What are The Hierarchy Semantics? • Inheritance Occurs From Parent to Child Only • Declaring Properties “Final” • Properties Set on a Child are “Protected” • Unlimited Hierarchy Depth
Open Question – Is a Config Portlet Mode Useful? • Allows Portlet Developer to Explicitly Prohibit User Customization of State • Allows Portlet Developer to Empower Consumer Administrators to Prohibit User Customization of State
Next Steps • Answer Open Questions • Finalize Use Cases and Feature Proposal • Begin Feature Specification