Hi,
I am workin in a application in which i need to maintain the last accessed UI state(like column filters, sortings, selected records, resized widgets, columns, etc) of the page throughout the app session, this only terminated on the session end(and ll be posted to db on the session end either by manual logout or browser close). i have few things to ask
I have a parent page that never refreshes(this is a framework page, and i don have control on this one). My page is on the frame, and this frame will be loaded with different pages on runtime. so i decided to create a list object in my parent page during runtime using like this
parent.parent.parent.eval("var sam;") and fill my state objects (in JSON form) during the whole session.
is it recommented using this kind of approach?? is it ok to maintain this amount of data in client side?? am not much into javascript oject deallocation capablitites.. will it hurt the system on anyway??
- And i am maintaining JSON data array in my page which holds the some data, and it ll be maintained only on the page lifetime, it ll be terminated on page unload.. and this can grow based on the data in the page
I just started worrying, can browser hold this burden?? can someone suggest me the javascript best approaches on performance..
Cheers
Ramesh Vel