Howdy.
Well. Due to my utter confusion over cflocks, I've gone in to my
shopping cart and got rid of ALL session variables and converted them
to client variables. I'm serializing the shopping cart variable
itself with WDDX for storage in the client storage database. All is
well I'm happy to report through my initial testing.
A couple of questions about client storage and cfid/cftoken.
1. Does anyone see a problem with creating the CGLOBAL and CDATA
tables right in the product database then specifying it as the client
storage database? Would that work or is it a DUMB idea? :) Would it
be better to create a separate database for client storage for each
app in case the host doesn't have a default database set up for
client storage? The data field grows quite rapidly when you enter
products into the cart so I don't think registry storage is a good
option. Seems like you wouldn't be fighting with other applications
on the server to be writing to the default database if it was self
contained within the application or the products database itself.
2. What exactly causes a browser to have a unique client.cfid and
client.cftoken? What are the chances of 2 browsers being on a server
with the same combination of cfid and cftoken?
3. What would happen in the slim chance someone else on the server
named their application the same as your's?
Thanks.
--
Bud Schneehagen - Tropical Web Creations
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
ColdFusion Solutions / eCommerce Development
[EMAIL PROTECTED]
http://www.twcreations.com/
954.721.3452
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
