Re: [WebDNA] 30 Minute Cookies
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112662
interpreted = N
texte = 245Chris,I was extremely happy to switch from [cart] based shopping cartsto [cookie] based carts -- because the use of cookies totallyeliminated all the problems related to passing cart values frompage to page. Cookies are SO MUCH BETTER for this task!And using the ip address (in whole or in part) to identify asession is a huge mistake in my opinion, because ISPs assign ipaddresses dynamically, changing them all the time, and they havedone it this way for decades.Your implementation of [session] would require that I go back topassing a session value in every link and form in the entirewebsite. This is practically impossible in anything but a newwebsite due to the extensive rewriting required. But it is notsomething I would consider even when creating a new website fromscratch -- because cookies are still far better at this task.Sorry Chris, I have no use for your [session] system and I'mwilling to bet that most everyone else feels the same. I honestlydo not know why you bothered to create it before asking us if wewould ever use it. You did the same thing with BioType.I wish you would just ask us what changes we might like to see inWebDNA, and make those changes first, before introducing newfeatures that no one asked for or wants or needs.Trying to anticipate the future and introduce new features toserve those potential future needs is great *if* your currentproduct is not lacking, and if you have the money to splurge ondeveloping new features no one may ever use. But this is not thesituation with WebDNA, is it?Updating WebDNA's cookie capabilities is something we could alluse today and into the foreseeable future. Some of us would alsofeel better about being able to offer our clients dramaticallysimplified and updated database security, perhaps in the way wediscussed a few weeks. These are the things we use every day.BTW, [session] is not listed on your alphabetical list of tags andcontexts. I wonder how many others are missing from this(alphabetical) list or the other (categorized) list?Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Administration> It is built with a specific number of information the browser> returns to the server, the browser IP, and a lifetime. WebDNA> (8.1+) creates a hash with the information, that you "move"> from page to page with a GET or a POST. You can then check the> hash anytime to see if the session is still alive, if the IP is> different from the original and if the browser changed.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list
.To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Associated Messages, from the most recent to the oldest:
245Chris,I was extremely happy to switch from [cart] based shopping cartsto [cookie] based carts -- because the use of cookies totallyeliminated all the problems related to passing cart values frompage to page. Cookies are SO MUCH BETTER for this task!And using the ip address (in whole or in part) to identify asession is a huge mistake in my opinion, because ISPs assign ipaddresses dynamically, changing them all the time, and they havedone it this way for decades.Your implementation of [session] would require that I go back topassing a session value in every link and form in the entirewebsite. This is practically impossible in anything but a newwebsite due to the extensive rewriting required. But it is notsomething I would consider even when creating a new website fromscratch -- because cookies are still far better at this task.Sorry Chris, I have no use for your [session] system and I'mwilling to bet that most everyone else feels the same. I honestlydo not know why you bothered to create it before asking us if wewould ever use it. You did the same thing with BioType.I wish you would just ask us what changes we might like to see inWebDNA, and make those changes first, before introducing newfeatures that no one asked for or wants or needs.Trying to anticipate the future and introduce new features toserve those potential future needs is great *if* your currentproduct is not lacking, and if you have the money to splurge ondeveloping new features no one may ever use. But this is not thesituation with WebDNA, is it?Updating WebDNA's cookie capabilities is something we could alluse today and into the foreseeable future. Some of us would alsofeel better about being able to offer our clients dramaticallysimplified and updated database security, perhaps in the way wediscussed a few weeks. These are the things we use every day.BTW, [session] is not listed on your alphabetical list of tags andcontexts. I wonder how many others are missing from this(alphabetical) list or the other (categorized) list?Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Administration> It is built with a specific number of information the browser> returns to the server, the browser IP, and a lifetime. WebDNA> (8.1+) creates a hash with the information, that you "move"> from page to page with a GET or a POST. You can then check the> hash anytime to see if the session is still alive, if the IP is> different from the original and if the browser changed.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Kenneth Grome
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:
MasterCounter and capitalization (1997)
[WebDNA] GETCHARS ... words? (2009)
[CART] inside a [LOOP] (1997)
WebCat2 several catalogs? (1997)
WebCatalog Technical Reference (1997)
insecuretextvars preference doesn't work (2000)
What about this gremlin issue? (2000)
Error: Too many nested [xxx] contexts (1997)
HELP WITH DATES (1997)
Sku numbers (1997)
Re:Searching for ALL / empty form field (1997)
Virtual hosting and webcatNT (1997)
multi-paragraph fields (1997)
4.0x on production server (2000)
Showif ~ Netscape : Showif ~ MSIE (2001)
Re:2nd WebCatalog2 Feature Request (1996)
[if] and [showif] (2002)
WebDNA Feature Request (2006)
a search based on ^(contains) (1998)
Multiple cart additions (1997)