Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db?

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113084
interpreted = N
texte = 672 Yes, or you can capture the IP and reload the session without passing = anything: you just compare the IP with the stored session IP and if it = matches then you can reload the session individually for each page. Or = you can use browserID. > On Oct 21, 2016, at 21:46, Kenneth Grome = wrote: >=20 > Don't you have to pass a parameter in links and forms to make it work? >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration >=20 >=20 >=20 > On 10/21/2016 01:27 PM, christophe.billiottet@webdna.us wrote: >> [session] is a built-in WebDNA process that very simply allows to = build a session. Compared to a cookie, it is easier to use (You don=E2=80=99= t have to care about the technical aspects of the cookie like date = format etc=E2=80=A6), safer (nothing is written on the visitor side), = faster (RAM based instead of being read and written to the browser), and = gives you a better control (you can kill a session very easily, or move = it from one browser to another if necessary) >> Instead of just being a serial number like the [ORDERFILE], if = follows without showing and keep information about the visitor. >> Information about a session is stored and can be used later. >>=20 >> - chris --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 2016)
  2. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 2016)
  3. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  4. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  5. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  6. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  7. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  8. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  9. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  10. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  11. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  12. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  13. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  14. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  15. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  16. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  17. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  18. [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 2016)
672 Yes, or you can capture the IP and reload the session without passing = anything: you just compare the IP with the stored session IP and if it = matches then you can reload the session individually for each page. Or = you can use browserID. > On Oct 21, 2016, at 21:46, Kenneth Grome = wrote: >=20 > Don't you have to pass a parameter in links and forms to make it work? >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration >=20 >=20 >=20 > On 10/21/2016 01:27 PM, christophe.billiottet@webdna.us wrote: >> [session] is a built-in WebDNA process that very simply allows to = build a session. Compared to a cookie, it is easier to use (You don=E2=80=99= t have to care about the technical aspects of the cookie like date = format etc=E2=80=A6), safer (nothing is written on the visitor side), = faster (RAM based instead of being read and written to the browser), and = gives you a better control (you can kill a session very easily, or move = it from one browser to another if necessary) >> Instead of just being a serial number like the [orderfile], if = follows without showing and keep information about the visitor. >> Information about a session is stored and can be used later. >>=20 >> - chris --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . christophe.billiottet@webdna.us

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:

Tech support (2000) [WebDNA] Did everything in ReadMe.txt and it still doesn't work (2013) append db wierdness (1999) This list needs a digest: rant, rave... (1997) Missing from Docs [folderName] (1997) Is there a max number of fields? (1998) Date fun with MySQL (2004) PIXO Support (1997) Am I going senile? (Price recalc based on quantity) (1997) [WebDNA] maybe silly suggestion? [founditems] (2015) WebTV problems with WebCatalog?? (1998) Extended [ConvertChars] (1997) notification solutions (1997) My Eyes doth deceive me (2002) problems with 2 tags (1997) [lookup] vs. [search] (1998) WebDNA Upgrade Problems (2003) [append] problem (1997) The [shownext] limitations (2002) Security Hole - NetCloak Update (1998)