I'm looking for some ideas to see an object's variables, cookies, reference cache, state, or a session Database.
I have a web form (ASPX) that will include many user controls that will act as a "page", and these controls are included on one-on-one-time-method:
< Pre> & lt; Uc1: UserControl1 id = "controlStep1" runat = "server" visible = "true" /> & Lt; Uc2: UserControl2 id = "controlStep2" runat = "server" visible = "false" /> & Lt; Uc3: UserControl3 id = "controlStep3" runat = "server" visible = "false" /> I have an object that I use to include various parameters. These parameters come in the form of query string values in the application and this object lazy loads them. For example: public class status {Private string _jobId; Private jobtip _ jobtip; Public String Job ID {Receive (if !! string.isnellOn White Space (_jobId)) back _jobId; _jobId = GetFromQueryString ("jid"); Return _ job; }} Public JobType Job Type {Receive (_jobType! = JobType.Default) _jobType; _jobType = GetEnumFromQueryString ("jtype", typef (jobtip)); Back _jobType; }}}
I would like to continue this situation, while the client is in the web application, proceed through a wizard-style interface, because user controls are toggle 'visibility At this time, I am making an example of the status object in an HTTP module during the customer's first request and it is available on HTTPTPTEX. Running I store it in items, but I would like to use lazy loading so that according to the requirement of different position object properties only load however, if for example a control control has reached Step1, I would like to continue the position of the object, So if the same property is accessed on controlStep2, then the gates do not have to go back to the query string. I request the value of the property I requested I can serialize and distribute in the HTT module, but if a property is accessed and full, then it will not be missed on the next request.
Any suggestions?
The file system is sometimes a useful persistance mechanism.
Comments
Post a Comment