Re: PHP and user login stuff

[Jason Pincin <jpincin@ashtech.net>]

> Hmmm, on second thought maybe a password in the URL (encrypted or not)
> isn't necessarily a good idea.

No.  It's not a good idea.  That stuff can still be snarfed and used,
encrypted or not.

> 
> Basically, it's either
> 1.  This (which requires all pages be generated dynamically)

Don't like that.

> 2.  The user enters handle/passwd EVERY time they do something requiring
> it

Like that if they choose not to use cookies.  It's not so bad.  Your not
going to have any one user running around commenting on dozens of
articles... and you don't need to login to say wether or not an article
helped you out.  If someone wants to spend an afternoon and make comments
on 50 articles, I'm sure they would consider a temporary cookie.

> > I think it's desirable to impliment both.  If Micah doesn't want to impliment the
> > cookie method now, thats fine, but at some point I'd want to go back and impliment
> > it.  Thats up to Micah.  Just like you'll have some users complain about
> Good idea - I'll probably start with what I described, then we can add
> and/or change it later.

Yeah... to make sure we're on the same page... I was thinking you just
impliment the method that requires a sign in everytime since it'd be
easiest... and re-usable once cookies are implimented... cuz we'll still
need it.

That is unless your further along with another method.  I was just curious
as to exactly what method you'll be doing first.

Let me know, I'm excited :)

> Also, the signup form is coming along.  There are a couple problems with
> it that I'm trying to debug.  It's in my home directory now, in
> public_html

Cool!