HighTechTalks DotNet Forums  

Page Caching - Is this the solution.

ASP.net Caching microsoft.public.dotnet.framework.aspnet.caching


Discuss Page Caching - Is this the solution. in the ASP.net Caching forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
AT
 
Posts: n/a

Default Page Caching - Is this the solution. - 04-02-2004 , 02:49 AM






Basically, I have a web app which has a step-by-step flow. So the user
fills a form, hits next and is taken to the next page, where the user
enters more information in form. There are around 5 steps for the user
to complete. Each step is on a different page.

The problem is that at any point the user should be able to go back
and see what he has filled in the previous screens.
How should this be achieved? Should I cache (at client?) the pages
completed by the user, so when the user hits the browser back button,
the pages with data is visible.
OR
Should I cache the viewstate of all the pages and check on every page
- if Viewstate Cache for that page exist, then get everything from
ViewState.
OR
There s any other recommender solution!!!!
Thanks

Reply With Quote
  #2  
Old   
Martin Dechev
 
Posts: n/a

Default Re: Page Caching - Is this the solution. - 04-02-2004 , 05:52 AM






You can make a user control for each page you have now and leave the
ViewState of the page worry about the persistance of the input.

The problem with this situation is that the ViewState for the page gets
quite large. I recommend either enabling http compression on the information
server or storing the ViewState on the server.

Hope this helps
Martin
"DJ Dev" <ricky.arora (AT) icn (DOT) siemens.com> wrote

Quote:
Basically, I have a web app which has a step-by-step flow. So the user
fills a form, hits next and is taken to the next page, where the user
enters more information in form. There are around 5 steps for the user
to complete. Each step is on a different page.

The problem is that at any point the user should be able to go back
and see what he has filled in the previous screens.
How should this be achieved? Should I cache (at client?) the pages
completed by the user, so when the user hits the browser back button,
the pages with data is visible.
OR
Should I cache the viewstate of all the pages and check on every page
- if Viewstate Cache for that page exist, then get everything from
ViewState.
OR
There s any other recommender solution!!!!
Thanks



Reply With Quote
  #3  
Old   
DJ Dev
 
Posts: n/a

Default Re: Page Caching - Is this the solution. - 04-02-2004 , 04:00 PM



Thanks for the reply. How can I make a user control of the whole page
I am not sure if this will solve my problem. Would client caching help in my case
I need more guidance I guess

Thanks!

---
Posted using Wimdows.net Newsgroups - http://www.wimdows.net/newsgroups/

Reply With Quote
  #4  
Old   
coollzh
 
Posts: n/a

Default Re: Page Caching - Is this the solution. - 04-02-2004 , 10:41 PM



i think you should make five panel ,and just hidden before and show next
panel when user fill the next form. when user go back,you can just show
before and hidden the current panel. it's simply

"DJ Dev" <ricky.arora (AT) icn (DOT) siemens.com> ????
news:1169423e.0404012349.4998c272 (AT) posting (DOT) google.com...
Quote:
Basically, I have a web app which has a step-by-step flow. So the user
fills a form, hits next and is taken to the next page, where the user
enters more information in form. There are around 5 steps for the user
to complete. Each step is on a different page.

The problem is that at any point the user should be able to go back
and see what he has filled in the previous screens.
How should this be achieved? Should I cache (at client?) the pages
completed by the user, so when the user hits the browser back button,
the pages with data is visible.
OR
Should I cache the viewstate of all the pages and check on every page
- if Viewstate Cache for that page exist, then get everything from
ViewState.
OR
There s any other recommender solution!!!!
Thanks



Reply With Quote
  #5  
Old   
Scott M.
 
Posts: n/a

Default Re: Page Caching - Is this the solution. - 04-03-2004 , 10:26 AM



This is what I was going to suggest. I think it is a much better approach
than having 5 web pages.


"coollzh" <coollzh (AT) hotmail (DOT) com> wrote

Quote:
i think you should make five panel ,and just hidden before and show next
panel when user fill the next form. when user go back,you can just show
before and hidden the current panel. it's simply

"DJ Dev" <ricky.arora (AT) icn (DOT) siemens.com> ????
news:1169423e.0404012349.4998c272 (AT) posting (DOT) google.com...
Basically, I have a web app which has a step-by-step flow. So the user
fills a form, hits next and is taken to the next page, where the user
enters more information in form. There are around 5 steps for the user
to complete. Each step is on a different page.

The problem is that at any point the user should be able to go back
and see what he has filled in the previous screens.
How should this be achieved? Should I cache (at client?) the pages
completed by the user, so when the user hits the browser back button,
the pages with data is visible.
OR
Should I cache the viewstate of all the pages and check on every page
- if Viewstate Cache for that page exist, then get everything from
ViewState.
OR
There s any other recommender solution!!!!
Thanks





Reply With Quote
  #6  
Old   
DJ Dev
 
Posts: n/a

Default Re: Page Caching - Is this the solution. - 04-06-2004 , 05:09 PM



Thanks for the replies guys. I started with Panels...but the problem is that my web App requires heavy processing and the code-behinds have lots n lots of lines with dynamic datagrids etc.

Integrating all this info into one file will be a big pain. Moreover designing with Panels is a very big pain
Anyother ideas?

Is there a way that the Viewstate of a page can be saved ( cache etc) or something and restored

Thanks!

---
Posted using Wimdows.net Newsgroups - http://www.wimdows.net/newsgroups/

Reply With Quote
  #7  
Old   
DotNetJunkies User
 
Posts: n/a

Default Re: Page Caching - Is this the solution. - 11-18-2004 , 01:36 PM



Try creating a class that contains the data for each page. Store the information into a session variable or as a XML file in a working folder. Use a unique ID as the file name. Pass that id across pages (QueryString).
As a new page is loaded with info, load the class and save the new data to this class. As an old page is recalled, pull the data from the class. At the end, get the data from the class and update your permanent data base.

atllc (AT) att (DOT) net



---
Posted using Wimdows.net NntpNews Component -

Post Made from http://www.DotNetJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.