What is the best way to store client variables? We are in the process of
completely redesigning our website and considering changing the clientstorage
attribute in cfapplication from a named SQL datasource to Cookie to prevent
having 100,000's of records pile up on our SQL server.
The primary
Database here.
Stay away from storing in cookies as much as possible.
On 4/26/07, james carberry [EMAIL PROTECTED] wrote:
What is the best way to store client variables? We are in the process of
completely redesigning our website and considering changing the
clientstorage attribute in
On 4/25/07, james carberry wrote:
What is the best way to store client variables?
Better way to phrase that is what is the least bad way? :-)
Cookies are a disaster. To make a long story short you can't count
on them being present all the time, and you have to wait for a trip to
the client
: Preferred clientstorage setting for client variables
What is the best way to store client variables? We are in the process of
completely redesigning our website and considering changing the clientstorage
attribute in cfapplication from a named SQL datasource to Cookie to prevent
having 100,000's
Writing to the db. As robust as your db is. Nobody loves a
thing that executes a db read and write at every page
request, but at least there are no vultures circling your
server when you do it this way. The problems you will cause
will be manageable, one way or the other.
Unless you
What is the best way to store client variables? We are in
the process of completely redesigning our website and
considering changing the clientstorage attribute in
cfapplication from a named SQL datasource to Cookie to
prevent having 100,000's of records pile up on our SQL server.
The
6 matches
Mail list logo
