Storing Objects in Session Object

[MrShovel]

I'm new to this ASP.NET caper and have the following questions.

I have a TestObject that contains about 50 fields of data and 3 member
procedures. Below is a simplified explanation of what I do.

At the start of each session I initialise this TestObject.

On entering every page I create a local TestObject and do this:
TestObject = Session("TestOb ject")

On leaving every page I do this:
Session("TestOb ject") = TestObject

This way my TestObject is kept across all the pages until my user quits
or the session times out. My site will probably have up to 100
concurrent sessions running.

Question 1:
Is there a better way to do what I've just described?
-------------------------------------------------
Question 2:
Which is the better way? (Efficient)
[assuming Test=Session("T estObject")]

Test.Field1.val ue = "1234"
or this?
Session("TestOb ject").Field1.v alue = "1234"

Is it quicker to manipulate a local object then put it into the Session
Object when finished?
-------------------------------------------------
Question 3:
Assuming the TestObject member procedures looks something like this:

Procudure SomeProc()
me.Field1.value = "1234"
'heaps more line like above...
'heaps more line like above...
End Sub
-------------------------------------------------
Would it be better to have this?

Procudure SomeProc()
ExternalProc(Me )
End Sub

And in an another module (local on the site)

Procudure ExternalProc(By Ref Test as TestObject)
test.Field1.val ue = "1234"
'heaps more line like above...
'heaps more line like above...
End Sub

I'm assuming that when you transfer a sessionobject into you code it
also has to transfer all the code defined in the Object Member
Procedures, so it those procedures only have a call to an externaly
referneced module (passing a pointer to the ojbect) then there is
hardly any code in the object itself?

Am I right in this?

Thanks....

[Karl Seguin]

#1:
There are different ways, but urs is good. I hate pining things in memory.
I'd prefer to store the data in the database and cache it, which gives you
the speed benefit of in memory (like a session) and the smaller footprint of
the database. It's hard to say though, it depends on how exactly it's
beeing used, you should profile

#2
It doesn't matter too much, but creating a local variable is probably better
(ie, your first example). Otherwise you need to do a hash lookup every
time.

#3
is where you are most-wrong. your alternative doesn't make any sense. Keep
the code in the procedure. Extra lines of code aren't stored in memory for
every instance. Just because the code of your object is big, doesn't
translate into large objects. It's all about hte data you store in them.

Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/
http://openmymind.net/redirector.aspx?documentId=51 - Learn about AJAX!

"MrShovel" <sh********@hot mail.com> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

I'm new to this ASP.NET caper and have the following questions.

I have a TestObject that contains about 50 fields of data and 3 member
procedures. Below is a simplified explanation of what I do.

At the start of each session I initialise this TestObject.

On entering every page I create a local TestObject and do this:
TestObject = Session("TestOb ject")

On leaving every page I do this:
Session("TestOb ject") = TestObject

This way my TestObject is kept across all the pages until my user quits
or the session times out. My site will probably have up to 100
concurrent sessions running.

Question 1:
Is there a better way to do what I've just described?
-------------------------------------------------
Question 2:
Which is the better way? (Efficient)
[assuming Test=Session("T estObject")]

Test.Field1.val ue = "1234"
or this?
Session("TestOb ject").Field1.v alue = "1234"

Is it quicker to manipulate a local object then put it into the Session
Object when finished?
-------------------------------------------------
Question 3:
Assuming the TestObject member procedures looks something like this:

Procudure SomeProc()
me.Field1.value = "1234"
'heaps more line like above...
'heaps more line like above...
End Sub
-------------------------------------------------
Would it be better to have this?

Procudure SomeProc()
ExternalProc(Me )
End Sub

And in an another module (local on the site)

Procudure ExternalProc(By Ref Test as TestObject)
test.Field1.val ue = "1234"
'heaps more line like above...
'heaps more line like above...
End Sub

I'm assuming that when you transfer a sessionobject into you code it
also has to transfer all the code defined in the Object Member
Procedures, so it those procedures only have a call to an externaly
referneced module (passing a pointer to the ojbect) then there is
hardly any code in the object itself?

Am I right in this?

Thanks....

[john_teague]

When you say
TestObject = Session("TestOb ject")

TestObject is a reference to Session("TestOb ject") any change to
TestObject will be reflected in the session variable. If there are
places where you need to make changes that don't effect the session
variable implement ICloneable interface.

If this is used on every page, you might consider making a BasePage
with a protected property to access the session variable. I prefer to
encapsulate persisted variable in a property, that way I know that
initialization will be handled regardless of what event/method I am in
on the page.

C#
protected TestObject test{
get{
TestObject o = (TestObject)Ses sion["TestObject "];
if(o == null){
//whatever I need to do to create the object for the first time
Session.Add("Te stObject", o);
}
return o;
set{
...
}
}

This could be on a base page class and all pages that inherit from it
will have access. Also, if you choose to change your persistence
medium (cache, straight from db) you only have to change it in one
place.

[MrShovel]

Thanks guys... will do further research & tests...