G
Guest
Hi,
I am building a single webform/webpage asp.net application using VB.NET.
I have created lots of classes for this web application.
On page load I use a facade controller pattern class to perform all my initial
class object instaniations using sub new() procedures
I'm using this project to learn the ins and outs of OOA and OOD, so instead
of doing everything in code behind pages I have lots of objects now created
with lots of properties.
My strategy for instance is to have objects with properties contain the
values of the currently selected web form object values (i.e. currently
selected item in list box) in
properites for an object instead of using the other method of simply reading
the value straight from the web object.
I am trying to keep business logic out of the interface object.
I don't know how to save my "session" objects so that when I click on a a
server side web interface object (ie. dropdown list box) I can save the new
selection to my object and not to code behind page objects.
Do I use session values the whole time, or view states, or cookies?
There would be an extra layer of extracting values if this is done:
1 create objects with initial properties.
2.put all my properties into session state value
3.interact with form, change session state values
4. recreate my object with a sub new procedure and pass all my session data
back into the object?
this seems like no return on investment architecturally or performance wise.
Can I save entire instantiated classes (objects) into a session variable?
If so , is this my answer?
thanks
Chris
I am building a single webform/webpage asp.net application using VB.NET.
I have created lots of classes for this web application.
On page load I use a facade controller pattern class to perform all my initial
class object instaniations using sub new() procedures
I'm using this project to learn the ins and outs of OOA and OOD, so instead
of doing everything in code behind pages I have lots of objects now created
with lots of properties.
My strategy for instance is to have objects with properties contain the
values of the currently selected web form object values (i.e. currently
selected item in list box) in
properites for an object instead of using the other method of simply reading
the value straight from the web object.
I am trying to keep business logic out of the interface object.
I don't know how to save my "session" objects so that when I click on a a
server side web interface object (ie. dropdown list box) I can save the new
selection to my object and not to code behind page objects.
Do I use session values the whole time, or view states, or cookies?
There would be an extra layer of extracting values if this is done:
1 create objects with initial properties.
2.put all my properties into session state value
3.interact with form, change session state values
4. recreate my object with a sub new procedure and pass all my session data
back into the object?
this seems like no return on investment architecturally or performance wise.
Can I save entire instantiated classes (objects) into a session variable?
If so , is this my answer?
thanks
Chris