Re: OT Cookie limit
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 37937
interpreted = N
texte = On 8/16/01 2:37 PM, John Peacock
wrote:> That you are asking this question at all is probably a good indication > that you are trying to do too much with cookies. Cookies are intended > to store small amounts of data to enable to web server to maintain > sessions. Every single time that a browser asks for a page, it sends > all applicable cookies. If you have 10 cookies * 4k * #users, you are > pretty quickly going to slow your system to a crawl, just with the > traffic due to cookies. > > Just store the session information in the shoppingcart or in another > database, then store the key in the cookie (can you say [cart]?).Actually I was asking, simply to know. I only have a few cookies set. But we are handling the store for the St. Louis Rams, but not the main site. We normally track referrer, search tags all within our own site. But We cannot since we do not have that original data. So I want them to pass them to me as cookies and then I will store them in the cart. But we also use cookies to store the cart, the users ID, and ZipPay Status, All very Small one liners. So I didn't want to hit a brick wall with critical data like User/Cart in exchange for referrer and search data.Since the rams main site developers are intimidated by our presence they don't want to share a whole lot of information. So we have to make it as easy as possible for them to get it to us. Additionally the rams use session cookies etc for the main info site and this will also strain the cookie issue.So for now I have the following Cookies Session ID (from Original Rams Site) session expire Session Auth Code (from Original Rams Site) session expire Cart ID session expire ZipPay Status Perpetual If they expand to use the Member Portion of MerchantMaker then they would use another cookie for the member status.BTW condescending tone not necessary, I may actually know what I am doing.Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, Unix, and AS/400.You best get your MIME right, and I mean RIGHT! ------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
On 8/16/01 2:37 PM, John Peacock wrote:> That you are asking this question at all is probably a good indication > that you are trying to do too much with cookies. Cookies are intended > to store small amounts of data to enable to web server to maintain > sessions. Every single time that a browser asks for a page, it sends > all applicable cookies. If you have 10 cookies * 4k * #users, you are > pretty quickly going to slow your system to a crawl, just with the > traffic due to cookies. > > Just store the session information in the shoppingcart or in another > database, then store the key in the cookie (can you say [cart]?).Actually I was asking, simply to know. I only have a few cookies set. But we are handling the store for the St. Louis Rams, but not the main site. We normally track referrer, search tags all within our own site. But We cannot since we do not have that original data. So I want them to pass them to me as cookies and then I will store them in the cart. But we also use cookies to store the cart, the users ID, and ZipPay Status, All very Small one liners. So I didn't want to hit a brick wall with critical data like User/Cart in exchange for referrer and search data.Since the rams main site developers are intimidated by our presence they don't want to share a whole lot of information. So we have to make it as easy as possible for them to get it to us. Additionally the rams use session cookies etc for the main info site and this will also strain the cookie issue.So for now I have the following Cookies Session ID (from Original Rams Site) session expire Session Auth Code (from Original Rams Site) session expire Cart ID session expire ZipPay Status Perpetual If they expand to use the Member Portion of MerchantMaker then they would use another cookie for the member status.BTW condescending tone not necessary, I may actually know what I am doing.Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, Unix, and AS/400.You best get your MIME right, and I mean RIGHT! ------------------------------------------------------------- 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://search.smithmicro.com/
Bob Minor
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:
3.0 to 4.0 (2000)
Re[2]: 2nd WebCatalog2 Feature Request (1996)
Kill the webcat process (2000)
[WebDNA] Date error (2017)
redirect with frames (1997)
port 16080 problem (2003)
removelineitems (2000)
WebCatalog for guestbook ? (1997)
Is this possible in simple search? question? (1998)
date formatting for CC card expiration date check (1998)
Help name our technology! (1997)
Solution help needed (1998)
Referrer (2000)
Java combo box with WebDNA database (2004)
[searchString] (1997)
Authentication Help (2000)
[append] problem (1997)
I'm tired of all this! (2000)
[WebDNA] Lookup vs. Search (was: 3-5 GB of native WebDNA db...) (2009)
Graphical display of sales volume (2003)