Session Objects

[soluga]

When I used to develop with classic ASP, I developed a number of applications that store shopping cart type information, in the begining I used to store the data in a session object, but found that if you tried to hold too many items in the session object it would have become unstable with unpredictable results, so I then used a temp database table and store the details with the session id which was normally their user id, this worked well but you had to keep clearing out the table, once the user had left.

Is this still the best way, or is there a better way in ASP.Net?

Thanks

[HoraShadow]

ASP.NET it's solid man.

Now it depends on the type of shopping cart that you want.
If you want to delete the customer's selections, then store them on sessions, use a DataTable for example.
If you want to keep it on a db, for the return of the customer, store it on the db and retrieve it later.

I say it again, it's solid man. You no longer have to worry about that stuff. That's history.

Now it's what fits you the most.

HTH
HoraShadow

[soluga]

Ta,
I was wondering about creating a datatable, but then I got to thinking thats fine in VB.Net, but with ASP.net being stateless, how can you keep the table in session, when you go from page to page??

[HoraShadow]

Sessions are mantained by the browser and the port they are connected to. This is transparent to us.

As long as the user uses the same browser window, and the session on the server doesn't expire, he has his information stored in sessions.

Keep in mind that sessions are ByRef. So when you refer it to a variable to work with, all the modifications you do to the variable are reflected inmediatly on the session value.

You should play like 10-15 minutes with sessions so you see how they work.

HTH
HoraShadow

[Wokawidget]

In the global.asax file there is an event for Session_End. Toast the DB data here.

Woof

[soluga]

I understand about sessions and data, it is the datatable concept that is throwing me.

[soluga]

Yep Session_End sounds best, I think.

there used to be a script for
WhileStillConnected, but will use the Session_End.

thanks

[Wokawidget]

Yep Session_End sounds best, I think.

there used to be a script for
WhileStillConnected, but will use the Session_End.

thanks

WhileStillConnected Script?

WOka

[soluga]

yeah, will dig it out and post back. it was used to test if the user was still connected to the session object

[mendhak]

If you have far too many session variables and users, you can also look into storing session variables in SQL Server.

[soluga]

as in a sqlserver table?

[Wokawidget]

yea...u can add a simple line to the web.config file that identifies the sql svr to use.
then all session vars are stored in there. this is a little slower than storing in memory, but releases resources on the web server.

woof

[soluga]

have been looking into this more and with V2.0 you can use the profile object!!

http://msdn.microsoft.com/library/de...erprofiles.asp