[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Adding Users
-----BEGIN PGP SIGNED MESSAGE-----
The only comment I have is regarding the user expiring/deleting. I'm cool
with purging from the DB the records after 30 days that are never used.
However once the user has logged in once their account should last
forever.
It's not like we're going to get 100,000's of user records. Nothing more
fustrating than trying to login with to an account that doesn't exist
anymore! And I doubt that people would re-create an account many time
before getting completely fed up.
Don't have the schema available, but it might be nice to have a
LastLoginDate field, so if later on down the road we want to impliment
this feature for some reason, we will already have the info. Also the
problem with TTL's is that you have to have a query run each day to
decrement all the records. Seems more efficiant to do a read and
evaluation than a read, decrement, and write.
- -Aaron "Don't listen to me about DB's 'cuz what do I know?" Turner
- --
Aaron Turner | Either which way, one half dozen or another.
aturner@pobox.com | Check out the Red Hat Linux User's FAQ Online!
www.pobox.com/~aturner | http://www.pobox.com/~aturner/RedHat-FAQ/
All emails from this account are PGP signed. Lack of a signature is "bad".
PGP Key fingerprint = FB E1 CE ED 57 E4 AB 80 59 6E 60 BF 45 1B 20 E8
On Tue, 9 Feb 1999, Jason Pincin wrote:
> > First Name - check that it's not blank
>
> Cool.
>
> > Last Name - same
>
> Cool.
>
> > MI - probably no check here. Not everyone has MI, and its not really
> > necessary anyway. Do we even need it in the DB?
>
> Might as well... some people may want full name displayed.
>
> > Handle: No check
>
> Cool.
>
> > Description - is this for US to fill out or should it be on the form?
>
> Should be on form. No check needed. Allows users to do a short "about
> me" blurb.
>
> > E-Mail - check that it has an @ and a . in that order (I guess...)
>
> Yes, do this check... but if it contains those, an email should be fired
> off with a random password that the user will use to log in for the first
> time, after which they are forced to change it. This verifys there valid
> email address.
>
> > Fake E-mail - no check
>
> Good.
>
> > Password - Check that it exists. How strict should we be on making it a
> > good password? Should we run it through a checker program that makes
> > sure it's not in the dictionary and is at least 5 characters?
>
> See E-Mail above... don't think this should be strict on basic level
> securitys... but on admin level... we may want to put a password checker
> in place. Thoughts?
>
> > Cookies - checkbox yes/no, no check needed
>
> Radio Button. Default Yes.
>
> > URL - no check
>
> Cool.
>
> > I assume the following would be set to defaults by the script:
> > UserID (auto-increment in Db)
>
> Correct.
>
> > RoleID (role with least priveleges)
>
> Correct. This value will be 1.
>
> > QperDay - what's this for exactly?
>
> Don't put this on form or handle it in script. This will be filled out
> via another procedure. Will always be NULL upon user sign-up. This
> relates to the email help-system we'll be putting in place eventually.
>
> > InceptTime (Current date/time)
>
> Right.
>
> > ModTime (same)
>
> Right.
>
> > TTL (null???)
>
> Should default to 30 days after ModTime at sign-up. This stands for
> Time-to-leave. If the user doesn't sign in for the first time in 30 days,
> the house cleaning scripts will delete this record. First time the user
> signs in this will be bumped up 90 days or whatever from there sign-in
> time... this takes care of stale/stagnant user records... or ones that
> gave an invalid email address.
>
> Comments?
>
> Jaosn
>
>
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNsDt3TM3jpXy1kJtAQEQ8AQAiIjN+G9wl5RhLrxqwu6ScA8aN/CPorjC
BnwvwY8k1kTk/cgrdbSPQiwbaiqOFpF2D1qL1TCzVNxUfksXGqdmc1Pv6pthf3gK
Vx8OcVOaUH4Ml/9x/P+sxca+whif8gow58sU2NjNoy3FZak2fMB5eKuPROCpdbPE
KzcRQH7Rrug=
=Qw7x
-----END PGP SIGNATURE-----