Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #14764
| From | "Phil Hunt" <aaa@aaa.com> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Storage of quasi-static data across pages |
| Date | 2012-06-29 10:23 -0400 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <jske8r$cu1$1@speranza.aioe.org> (permalink) |
| References | <jsi6hg$gfb$1@news.albasani.net> |
If you are using .net asp, you can store any object in the Session variable.
You need to cast it to the type after you retrieve.
Or, use a DB
Or, store the information in an xml fragment in session variable
"Stefan Weiss" <krewecherl@gmail.com> wrote in message
news:jsi6hg$gfb$1@news.albasani.net...
> In a large web application (intranet only, reasonably modern browsers),
> we have certain pieces of data which are created on the server and need
> to be available to the client on every page. This includes, among other
> things, a hierarchical menu structure and a list of message strings (not
> hierarchical yet, but they will be).
>
> The menu structure contains ~100 items and can be assumed to remain
> static as long as the user's group membership and permissions don't
> change.
>
> The messages include generic error messages ("Field %s does not contain
> a valid date"), specific error messages ("If you do X on this page, you
> also need to do Y."), as well as generic and specific status messages
> and some informational text strings. These strings are shared between
> the server and the client, because all form input is validated in both
> places. There are ~500 messages for one language, totalling ~30k bytes.
>
> We already have a mechanism in place to reduce the constant
> re-transmission of menu and messages, but it's too complicated and not
> entirely effective. Now the application is due for a complete
> rewrite/redesign, and I was wondering about the best way to store that
> data on the client between page loads.
>
> The goal is to reduce network traffic, increase page load speed, and if
> possible reduce the load on both server and clients.
>
> Two main options come to mind: the browser cache and local storage. Both
> will be available and enabled, and I can see both working equally well.
>
> What are your opinions on which to prefer in the described environment?
>
> - stefan
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Storage of quasi-static data across pages Stefan Weiss <krewecherl@gmail.com> - 2012-06-28 20:07 +0200
Re: Storage of quasi-static data across pages "Tom de Neef" <tdeneef@qolor.nl> - 2012-06-29 15:49 +0200
Re: Storage of quasi-static data across pages "Phil Hunt" <aaa@aaa.com> - 2012-06-29 10:23 -0400
Re: Storage of quasi-static data across pages Scott Sauyet <scott.sauyet@gmail.com> - 2012-06-29 13:44 -0700
Re: Storage of quasi-static data across pages Stefan Weiss <krewecherl@gmail.com> - 2012-06-30 04:03 +0200
Re: Storage of quasi-static data across pages Scott Sauyet <scott.sauyet@gmail.com> - 2012-07-05 04:09 -0700
Re: Storage of quasi-static data across pages Stefan Weiss <krewecherl@gmail.com> - 2012-07-06 00:36 +0200
csiph-web