Re: cookie based login process
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 60432
interpreted = N
texte = On Fri, 10 Dec 2004 16:39:05 -0600 Clint Davis
wrote:> On 12/10/04 4:16 PM, "eLists" wrote:>> That seems to be about it I think. Now the tough part, what kind of>> data do any of you store in cookies, balancing privacy concerns with>> having enough usable data in said cookies to not have to do a ton of>> additional searches on each page?> I usually store a Customer ID that corresponds to a record in the >database.> That way, you're not keeping anything in the cookie that private. >Then, you> can do a [search] or [lookup] to find anything you need to know. My thought to store a bit more in the cookies is to be able to do things like proximity searches without having to do an extra search (this is a dating site). So if I stored the location of the user and I know the location of the profile they are viewing I don't have to do that extra search.Probably for round 1 I will do as you suggest and only store their ID. I really want to tread carefully on the privacy vs. usability line. >> Do end users get uncomfortable when things like their city, state,>> country are stored in a cookie?> Some end users will get uncomfortable if you store ANYTHING. The >best bet is> to outline everything in your privacy policy so they know what >they're> getting into when the submit info on your site.I current store some cookies for my chat, and I do say that in the privacy policy. I also have a page where they can view all cookies set by the site as well as clear them. I have had this on the site for about 4 years already :) I don't hide anything from themThank you for the input.Dale-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
On Fri, 10 Dec 2004 16:39:05 -0600 Clint Davis wrote:> On 12/10/04 4:16 PM, "eLists" wrote:>> That seems to be about it I think. Now the tough part, what kind of>> data do any of you store in cookies, balancing privacy concerns with>> having enough usable data in said cookies to not have to do a ton of>> additional searches on each page?> I usually store a Customer ID that corresponds to a record in the >database.> That way, you're not keeping anything in the cookie that private. >Then, you> can do a [search] or [lookup] to find anything you need to know. My thought to store a bit more in the cookies is to be able to do things like proximity searches without having to do an extra search (this is a dating site). So if I stored the location of the user and I know the location of the profile they are viewing I don't have to do that extra search.Probably for round 1 I will do as you suggest and only store their ID. I really want to tread carefully on the privacy vs. usability line. >> Do end users get uncomfortable when things like their city, state,>> country are stored in a cookie?> Some end users will get uncomfortable if you store ANYTHING. The >best bet is> to outline everything in your privacy policy so they know what >they're> getting into when the submit info on your site.I current store some cookies for my chat, and I do say that in the privacy policy. I also have a page where they can view all cookies set by the site as well as clear them. I have had this on the site for about 4 years already :) I don't hide anything from themThank you for the input.Dale-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"eLists"
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:
Emailer setup (1997)
Saving Text Areas with Orders (1997)
[SMSI] WebDNA is too good to go away! (2006)
shell question (2004)
finding the next thursday (2000)
Windows nt service pack 3 upgrade (1997)
Follow-Up to: Removing [showif] makes a big difference in speed (1997)
Using a database with a short url (2000)
PCS Frames (1997)
add to cart within a page? (1997)
Unable to view next 101-200 (1997)
multiGroupChecker code redundant? (2000)
Summing a field full of numbers ... (1997)
For those of you not on the WebCatalog Beta... (1997)
WebCatalog and Macromedia Flash (1998)
Putting a page between checkout and invoice (1999)
TeaRoom Order fields email account remain empty even thoughthewy are filled. (1997)
[WebDNA] Styling search results [using css] (2009)
Submit buttons not working.... (1999)
WebCatalog Use Question (1997)