1 / 9

WSRP Interfaces

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.

mccoym
Télécharger la présentation

WSRP Interfaces

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WSRP Interfaces Consumer Defined Portlet Hierarchies

  2. Goals • Introduction of Feature to TC • Gather Feedback To Use Within Subcommittee Discussion

  3. Feature Status • Initial Feature Proposal Draft • Some Subcommittee Email Discussion

  4. 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

  5. General Approach • Introduce CCP Hierarchies

  6. 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

  7. 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

  8. 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

  9. Next Steps • Answer Open Questions • Finalize Use Cases and Feature Proposal • Begin Feature Specification

More Related