Re: Package Proposal: Preference_Manager
| From: | Stig S. Bakken | Date: | Sun, 15 Dec 2002 21:09:33 +0000 |
| Subject: | Re: Package Proposal: Preference_Manager | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-11687@lists.php.net to get a copy of this message | ||
On Sat, 14 Dec 2002, Martin Jansen wrote:
> On Fri Dec 13, 2002 at 10:3425AM +0100, Stig S. Bakken wrote:
> > On Sun, 2002-12-08 at 22:30, Martin Jansen wrote:
> > > On Sat Dec 07, 2002 at 09:0645PM +0000, Jon Wood wrote:
> > > > Jon Wood wrote:
> > > > >>>I'd like to propose a new package, and I'm looking for the
> > > > >>>right
> > > > >>>name to
> > > > >>>give it, it's a small class for managing user preferences in an
> > > > >>>application, with basic session based caching of the values, and the
> > > > >>>ability to get default values if the user wants it to.
> > >
> > > +1 on this.
> > >
> > > > How about Authentication/PrefManager?
> > >
> > > Sounds ok for me.
> >
> > Uhm, what do preferences have to with authentication?
>
> That was my first thought also. But actually you need to authenticate
> the user in some way to load the preferences for him.
Sure, but does that relation need to be reflected in the preference
handling package?
The way I see this, authentication is just a way of establishing identity,
but a preferences package would be useful for managing per-package or
per-application settings well as per-user settings. Binding the name to
"auth" kinda limits the scope to users only.
- Stig