Jon Stevens wrote:
>
> Hey ppl...please try to keep messages here instead on the jserv-dev list...
Uh, sorry I posted another reply to the jserv-dev, before seeing the
message I'm replying to.
> 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.
Yup. I missed that.
So the sequence of actions is
user.setConfirmed(randomjunk);
...
if(user.getConfirmed() == suppliedjunk)
{
user.setConfirmed(User.CONFIRM_VALUE);
}
...
So, if we are trying to provide convinience methods,
setConfirmed(false) could generate the random confirmation code
and setConfirmed(true) could set the field to User.CONFIRM_VALUE.
if the user doesn't like that, there's always setConfirmed(String)
What about that?
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
