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:
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:
Expiration of Carts (1997)
[WebDNA] Ubuntu 11.10 (2012)
Simple question (1998)
forms and variables (1998)
Fedora Core 6 (2007)
(1998)
Re:Need help... (1997)
Searching blank fields problem (1999)
HELP WITH DATES (1997)
WebCat and Flash (2000)
HTTP header line is too long? (1997)
Support suggestions - long (was politeness, et al) (2000)
Multiple instances of database (2003)
emailer (1997)
[WriteFile] problems (1997)
Re:Version 2.0 and 1.6 simultaneous (1997)
Final invoice problems (1998)
Emailer problem (2000)
Editing Users.db (1997)
Re: (1997)