Re: Log-in Scheme

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 48583
interpreted = N
texte = Dan Strong wrote:> Howdy, > > I know I asked this over the summer and I will check the archives, but > in the meantime, can anybody offer advice on a decent log-in scheme > *that doesn't require cookies* for a fairly busy site? > > I seem to remember having users register and then write their > [encrypt]password[/encrypt] directly to WebDNA's users.db, and then > put [protect] tags on every page requiring log-in. This is what > [protect] is for, right? Any gotchas I should consider? > > Thanks in advance,It seems to me there are two functions being talked about with this subject.1) A Log-in system 2) protection based on log-inA simple log-in might consist of having a customer/accounts database that contains a username / pass and profile information. When a person goes to log-in they fill out a user/pass field and their info can then be written to the [cart] (session).It seems like to me that it wouldn't be an issue to write access info to the cart also (As Ron mentioned) to a [header1-40]. Which takes more resources.. opening an orderfile or doing a search? (probably either is close to the same). However, which takes less code? I would say:[orderfile cart=[cart]] [showif [header25]=level1] [/ordefile]might be an easier include?-- but they both seem easy enough -- can anyone think of a reason not to use a header?Donovan> > > -Dan > -- -Donovan Brooke -Administrator of IT / -Assc. Art Director -Creative Services -Epsen Hillmer Graphics-402.342.1169 X297 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Log-in Scheme (Donovan home EHG 2003)
  2. Re: Log-in Scheme (Kenneth Grome 2003)
  3. Re: Log-in Scheme (Clint Davis 2003)
  4. Re: Log-in Scheme (Alex McCombie 2003)
  5. Re: Log-in Scheme (Donovan 2003)
  6. Re: Log-in Scheme (Dan Strong 2003)
  7. Re: Log-in Scheme (Dan Strong 2003)
  8. Re: Log-in Scheme (Donovan 2003)
  9. Re: Log-in Scheme (Donovan 2003)
  10. Re: Log-in Scheme (Dan Strong 2003)
  11. Re: Log-in Scheme (Dan Strong 2003)
  12. Re: Log-in Scheme (Alex McCombie 2003)
  13. Re: Log-in Scheme (Bob Minor 2003)
  14. Re: Log-in Scheme (Dan Strong 2003)
  15. Re: Log-in Scheme (Dan Strong 2003)
  16. Re: Log-in Scheme (Dan Strong 2003)
  17. Re: Log-in Scheme (Alex McCombie 2003)
  18. Re: Log-in Scheme (Joe D'Andrea 2003)
  19. Re: Log-in Scheme (WebCat @ Inkblot Media 2003)
  20. Re: Log-in Scheme (Alex McCombie 2003)
  21. Re: Log-in Scheme (Dan Strong 2003)
  22. Re: Log-in Scheme (Dan Strong 2003)
  23. Re: Log-in Scheme (Alex McCombie 2003)
  24. Re: Log-in Scheme (Alain Russell 2003)
  25. Re: Log-in Scheme (Dan Strong 2003)
  26. Log-in Scheme (Dan Strong 2003)
Dan Strong wrote:> Howdy, > > I know I asked this over the summer and I will check the archives, but > in the meantime, can anybody offer advice on a decent log-in scheme > *that doesn't require cookies* for a fairly busy site? > > I seem to remember having users register and then write their > [encrypt]password[/encrypt] directly to WebDNA's users.db, and then > put [protect] tags on every page requiring log-in. This is what > [protect] is for, right? Any gotchas I should consider? > > Thanks in advance,It seems to me there are two functions being talked about with this subject.1) A Log-in system 2) protection based on log-inA simple log-in might consist of having a customer/accounts database that contains a username / pass and profile information. When a person goes to log-in they fill out a user/pass field and their info can then be written to the [cart] (session).It seems like to me that it wouldn't be an issue to write access info to the cart also (As Ron mentioned) to a [header1-40]. Which takes more resources.. opening an orderfile or doing a search? (probably either is close to the same). However, which takes less code? I would say:[orderfile cart=[cart]] [showif [header25]=level1] [/ordefile]might be an easier include?-- but they both seem easy enough -- can anyone think of a reason not to use a header?Donovan> > > -Dan > -- -Donovan Brooke -Administrator of IT / -Assc. Art Director -Creative Services -Epsen Hillmer Graphics-402.342.1169 X297 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Donovan

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Hiding HTML and page breaks (1997) Field Contents Raw (1999) [orderfile Orders/[cart]] (2000) Dates! (1998) using cookies to prevent access (2000) Bugs in IE 6.0 ? (2003) Help name our technology! (1997) insert graphic in email (2000) NT b19 sends extra MIME headers (1997) Date sorting (1997) Not really WebCat (1997) What's wrong with this [append] context? (2000) WebCat2_Mac RETURNs in .db (1997) OT: Collaborative Browsing (2000) RE: [WebDNA] Duplicate emails from list [WAS Ping....testing....1..2..3..] (2009) Search in 2 or more catalogs (1997) Location of Browser Info.txt file (1997) Reverse dating (1999) Questions To Answer (1997) Online reference (1997)