Hey ppl...please try to keep messages here instead on the jserv-dev list...
thx...
on 1/18/01 6:26 PM, "Rafal Krzewski" <[EMAIL PROTECTED]> wrote:
> getConfirmed/setConfirmed methods are build on top of getPerm/setPerm,
> therefore
> they are completly safe WRT LDAP and other backends.
>
> I must say that I don't like
> setConfirmed( boolean, String ) 'if false provide a value' aproach.
> It's counter intuitive and error prone in my opinion.
I agree.
> I'd suggest providing these methods, to make the two options orthogonal:
>
> void setConfirmed( boolean ) // toggle between CONFIRM_VALUE and ""
>
> void setConfirmedStatus( String )
>
> String getConfirmedStatus()
I still think that you are missing the point of the confirm field though.
The point is that the user is given a key which they need to provide in
order to go from not confirmed to confirmed. At no point (when using this
mechanism), should you have a "" as the confirmed portion of the database.
The process is like this:
new user object
populate new user object (set the confirmed key random string value)
create new user
then
user must supply the confirmed key received in email in order to confirm
their account at which point, it is changed from the random string to
User.CONFIRM_VALUE.
it isn't a "status" type of value.
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
