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:

Alternating BGColors in Table Rows (1998) WCS Newbie question (1997) pc (1997) Not reading code (1997) WebCat B13 Mac CGI -- Frames question (1997) WebCatalog for Postcards ? (1997) WC 2.0 frames feature (1997) Re:2nd WebCatalog2 Feature Request (1996) HTML E-mails demystified (2002) Trouble with formula.db (1997) Occasional crashes with $remove (1997) WebTen and WebCat (1997) [CART] inside a [LOOP] (1997) Cold Fusion Buster (1997) TCPconnect issue (2000) WebCat and WebTV (1997) Cart doesn't interpret tag! (1997) Dumb Question about Docs (1997) Faxing orders in place of email (1997) Generating Report Totals (1997)