View Single Post
  #4 (permalink)  
Old April 28th, 2009, 03:18 PM
ZeroFactorial ZeroFactorial is offline
Authorized User
 
Join Date: Mar 2009
Posts: 79
Thanks: 4
Thanked 4 Times in 4 Posts
Default

Quote:
Originally Posted by AspNew View Post
Using MVC is one way :).
The book that Vince has put together is in a nutshell MVC if you compare what he has done against the MVC model.

MVC meaning Model, View, Controller is the same three layer process that Vince followed. The issue of ViewState vs Cache is purely choice and has nothing to do with software architectural pattern. To me they both accomplish the samething.

With that being cleared up and correct me if Im wrong.
To me Viewstate is my preferred choice from a security standpoint. Cache can be comprimised after the page no longer exists. With ViewState it only exists on that one page while that page is present. So if you go to a new page no more data, with Cache you get easier access to the data but it exists until you destroy it.