Re: Shop from PDF
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59807
interpreted = N
texte = Dan, You'll save yourself a lot of time and trouble if you get over your dislike of cookies. Tying a cart and client browser together is very much what cookies were designed to do - they're easy to implement, effective and pretty much universally accepted. You're likely to run into problems tracking people by IP, eg someone inside AOL will send requests from different IP's in the same browser session as requests are sent from an array of caching servers. Rob > From: "Dan Strong"
> Date: October 27, 2004 1:23:46 PM EDT > Subject: Re: Shop from PDF > > > I guess that's essentially what I am doing with the temp.db. Client > (and I) don't care much for cookies, so I guess I'll just press > forward as planned. Thanks for the advice. > -Dan > > > On Wed, 27 Oct 2004 09:15:57 -0700 > Sam Lewis wrote: >> >> Dan, >> >> You could use a cookie based cart id. When they add the first item to >> the cart just write a cookie with their cart number. Then when they >> come back use the cookie to tie it to the first cart item. >> >> Sam >> >> >>> Hi all, >>> >>> I have a scenario in the works where a person will download a PDF >>> catalog and all of the products have been hotlinked to the item in >>> the online store. Once there they can add to cart like normal and >>> all is fine except that if they 'shop' from the PDF again it clears >>> the cart (as expected). I need to get around this. Dynamically >>> populating the PDFs with unique cart #'s is not a viable option at >>> this time. >>> >>> Right now, my thinking is to make a temp.db that basically has DATE >>> TIME IP CART and then if they click another link from the PDF, there >>> is some logic in the header of the store ([included] on all pages, >>> of course), that checks the IP and if it is a 'fresh' IP (say, less >>> than an hour old or something), then the cart associated with the IP >>> is used, and, in theory, would repopulate the cart correctly with >>> any existing items. >>> >>> Only prob I can see with this is that the .db would get pretty >>> unwieldy as it would pretty much become a traffic counter and could >>> get unwieldy quick, so now I would need to constantly roll this .db, >>> which seems like overkill... any thoughts before I dive in? Is there >>> anything obvious I am missing? >>> >>> Thanks in advance, >>> -Dan ------------------------------------------------------------- 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:
Dan, You'll save yourself a lot of time and trouble if you get over your dislike of cookies. Tying a cart and client browser together is very much what cookies were designed to do - they're easy to implement, effective and pretty much universally accepted. You're likely to run into problems tracking people by IP, eg someone inside AOL will send requests from different IP's in the same browser session as requests are sent from an array of caching servers. Rob > From: "Dan Strong" > Date: October 27, 2004 1:23:46 PM EDT > Subject: Re: Shop from PDF > > > I guess that's essentially what I am doing with the temp.db. Client > (and I) don't care much for cookies, so I guess I'll just press > forward as planned. Thanks for the advice. > -Dan > > > On Wed, 27 Oct 2004 09:15:57 -0700 > Sam Lewis wrote: >> >> Dan, >> >> You could use a cookie based cart id. When they add the first item to >> the cart just write a cookie with their cart number. Then when they >> come back use the cookie to tie it to the first cart item. >> >> Sam >> >> >>> Hi all, >>> >>> I have a scenario in the works where a person will download a PDF >>> catalog and all of the products have been hotlinked to the item in >>> the online store. Once there they can add to cart like normal and >>> all is fine except that if they 'shop' from the PDF again it clears >>> the cart (as expected). I need to get around this. Dynamically >>> populating the PDFs with unique cart #'s is not a viable option at >>> this time. >>> >>> Right now, my thinking is to make a temp.db that basically has DATE >>> TIME IP CART and then if they click another link from the PDF, there >>> is some logic in the header of the store ([included] on all pages, >>> of course), that checks the IP and if it is a 'fresh' IP (say, less >>> than an hour old or something), then the cart associated with the IP >>> is used, and, in theory, would repopulate the cart correctly with >>> any existing items. >>> >>> Only prob I can see with this is that the .db would get pretty >>> unwieldy as it would pretty much become a traffic counter and could >>> get unwieldy quick, so now I would need to constantly roll this .db, >>> which seems like overkill... any thoughts before I dive in? Is there >>> anything obvious I am missing? >>> >>> Thanks in advance, >>> -Dan ------------------------------------------------------------- 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/
Robert Schmidt
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:
[foundItems] context question --returns some fields but not others-- (2000)
Format Thousands Looks Busted (2000)
Problem with broken images (2004)
RE: Loss in form (1998)
Accentued characters in emails (2000)
Re:no [search] with NT (1997)
Payment Processors (2005)
WebCat2 - [include] tags (1997)
Change in Host? (1999)
WC2/Mac -- Forms not submitting correctly with Mac browsers (1997)
Superfilous Characters (1998)
Spiders (1998)
OK, here goes... (1997)
[WriteFile] problems (1997)
japanese characters (1997)
HomePage Caution (1997)
Further on formula.db failure to calculate shipCost (1997)
notification solutions (1997)
[WebDNA] sem_open bugfix for os x version 6.2 (2012)
WebCat NT v. Mac (1997)