Developer forum

Hi Peter

You can set up the number of days the cart should be remembered. This is handled by a cookie and therefore not depending on the session.

Good idea with the ability to set the session timeout though.

Nicolai

Ah okay, but mb the user that reported timeout on basket was an extranet user who was logged out. or some other strange behaviour.
I would anyway be great if any session times or the like that would have an impact on user behaviour could be customized.

thanks :-)

 

Regarding the session timeout, you should really avoid increasing the general session length. If data is kept in the session for a long period of time for all users, then you are likely to run into memory issues when the site gets a lot of traffic.

The session should only be kept alive if it is absolutely necessary. You can accomplish this by sending keepalive/heartbeat requests to the server. See solution here: http://stackoverflow.com/questions/1431733/keeping-asp-net-session-open-alive

I have used that approach with great success on websites that has forms with a lot of fields. The script was not included on all pages, just the pages with forms.

In your case, you could run the script on all pages, but only if something has been added to the cart.

Does it make sense? Let me know what you think :)

Thanks Morten, that is exactly why I want it to be a part of the settings in the Administration, so that Dynamicweb can take all precautions on the subject.
I am sure that someone will copy your approach on the matter, so the best solution available will be implemented.

Great to hear an IRL example of the implementation regarding performance.