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

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113085
interpreted = N
texte = 673 What about the case where a company, school or organization has its = network behind a single NAT'd address? There would be an unknown number = of unique visitors with the same IP address, and for some companies, the = same exact browser is also a requirement. -MD > On Oct 21, 2016, at 11:55 AM, christophe.billiottet@webdna.us wrote: >=20 > 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. >=20 >=20 >=20 >=20 >=20 >> 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 >=20 >=20 >=20 >=20 >=20 > --------------------------------------------------------- > 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 --------------------------------------------------------- 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 (WebDNA Development 2016)
  3. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 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 (Kenneth Grome 2016)
  6. Re: [WebDNA] User sessions - cookies only or cookies and a (Kenneth Grome 2016)
  7. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 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 (Kenneth Grome 2016)
  10. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  11. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 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? (Donovan Brooke 2016)
  14. Re: [WebDNA] User sessions - cookies only or cookies and a (Kenneth Grome 2016)
  15. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  16. Re: [WebDNA] User sessions - cookies only or cookies and a (Michael Davis 2016)
  17. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  18. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  19. Re: [WebDNA] User sessions - cookies only or cookies and a (Kenneth Grome 2016)
  20. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  21. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  22. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Donovan Brooke 2016)
  23. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (Tom Duke 2016)
  24. Re: [WebDNA] User sessions - cookies only or cookies and a sessions.db? (christophe.billiottet@webdna.us 2016)
  25. [WebDNA] User sessions - cookies only or cookies and a sessions.db? (dale 2016)
673 What about the case where a company, school or organization has its = network behind a single NAT'd address? There would be an unknown number = of unique visitors with the same IP address, and for some companies, the = same exact browser is also a requirement. -MD > On Oct 21, 2016, at 11:55 AM, christophe.billiottet@webdna.us wrote: >=20 > 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. >=20 >=20 >=20 >=20 >=20 >> 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 >=20 >=20 >=20 >=20 >=20 > --------------------------------------------------------- > 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 --------------------------------------------------------- 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 . Michael Davis

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:

image attachment (2002) re: Large databases in WebCat (1997) Round up prices (2000) Suffix or Line? (1999) Fwd: 502 Bad Gateway (1998) Date Range Sorting (1997) Purchased cart being overwritten - still !?? (1997) Roundup function? (1997) [WebDNA] upload image files.... (2018) WebStar Questions ... (2000) WC2b15 - [HTMLx]...[/HTMLx] problems (1997) Paymethod question (1999) [WebDNA] Fails from http:// but works from file:/// (2009) best way to store prefs (1998) HELP..Changing Price after adding to cart. (1999) Problems searching from a FORM (1997) % (mod) was looping table rows (1999) User/Pass dialogue issue [AOL?] (2002) Re:HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997) [WebDNA] agree? --> also broken when we compare against something with a "!" in it. (2009)