[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp-interfaces] [wsia][wsia-wsrp joint interfaces] Hierarchicalproperties?
I certainly have no objection to this in principle, but what I want most is a clear templating mechanism. Ciao, Rex At 4:47 PM -0700 7/25/02, Alan Kropp wrote: >At one time, we were discussing support for a hierarchical property >mechanism. I realize we haven't talked about this lately, while we're still >fleshing out session/state protocol, but I thought I'd ping the group now so >that this doesn't fall below the radar. > >In brief, hierarchical properties enable the portlet developer, portal >admin, user, et al to "layer" values for a given property, based on some >external criteria. A typical set of layers for a property might look like >this: > >1. Default: What the property will take as a value, if no one has set a >value in a "higher" layer >2. Admin: The value specified by the administrator. This may be >overridden by... >3. User: The value the user provides. > >This matches JSR 168 Preferences behavior, and certainly enhances >interoperability between the two specs. > >Thoughts? > >Alan > > > >---------------------------------------------------------------- >To subscribe or unsubscribe from this elist use the subscription >manager: <http://lists.oasis-open.org/ob/adm.pl> -- Rex Brooks Starbourne Communications Design 1361-A Addison, Berkeley, CA 94702 *510-849-2309 http://www.starbourne.com * rexb@starbourne.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC