Yes such as a GUID but it doesn't have (and shouldn't be IMO) the profile
GUID (to avoid giving away an information that could be used some later day
maliciously).
I was thinking rather to something like a "job id".
The whole process would be :
- the user registers a new mail address (I suppose it goes in a child table
of its profile with its own unique id)
- register in the job table a new job with its unique id and the id of the
mail address to validate
- send the validation link
When the user clicks the link :
- retrieve the id of the mail to validate from the job table
- update the address record to mark the address as validated
- delete the record from the job table
If the user is allowed to change its mail, you may want also to do the same
process so that the updated address is validated (though it could be still
the same record id in the db).
Something along these lines...
Patrice
--
"Amir Ghezelbash" <am*****@rogers.com> a écrit dans le message de
news:ua**************@tk2msftngp13.phx.gbl...
you mean a GUID ...if i do that ..then how would i know which email is
it that they are trying to validate ?
their account could have more then one email address!
i have to somehow include the email address inot the link
---
Best Regards
Amir
*** Sent via Developersdex http://www.developersdex.com ***