B
bozzzza
Hi All,
We have a busy website, and I was wondering if we should persist the
data by storing the data table in a session or cookie, and when the
user re-loads the page I can cast the session or cookie back to a
datatable and rebind to the grid.
This is a closed web system so there is no problem getting users to
make sure cookies & javascript is enabled.
When the user clicks refresh for example it will re-load from the sql
server again.
But I am wondering if this is a good idea, apart from the obvious
problem of the data being out of date until the user clicks refresh,
are there any other problems this may cause like using more memory on
the server?
TIA
We have a busy website, and I was wondering if we should persist the
data by storing the data table in a session or cookie, and when the
user re-loads the page I can cast the session or cookie back to a
datatable and rebind to the grid.
This is a closed web system so there is no problem getting users to
make sure cookies & javascript is enabled.
When the user clicks refresh for example it will re-load from the sql
server again.
But I am wondering if this is a good idea, apart from the obvious
problem of the data being out of date until the user clicks refresh,
are there any other problems this may cause like using more memory on
the server?
TIA