You could also consider putting the cart into a fast memory store such as Redis, memcached or APC and then storing it into the database later. Sessions can be stored in memcached by default also: http://blog.simonholywell.com/post/374206138/installing-apc-and-memcached-for-php-sessions-on-ubuntu
On 15 July 2010 07:44, nicolaas <[email protected]> wrote: > Hi Folk > > Are there any arguments for or against the use of session for saving > cart information before committing it to a database (usually at the > moment of sale confirmation)? > > For: > * less database clutter > * faster? > > Against: > * more code > * less information on potential sales is retained in database > > Other things to consider are: > * can save some stuff, but not all > * security / privacy matters > * database maintenance / clean up procedures > * length of session > * ?????? > > I am welcoming any comments, for and against, just curious to know if > there are any "best practices" in this area. > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected]<nzphpug%[email protected]> > -- Simon Holywell http://www.simonholywell.com -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
