Storing Custom objects (class) and/or Scripting.Dictionary Objects in Application.Object Variablers
Posted on 2003-11-03
I am making a multilanguage script for a forum and was thinking of reading language files with filesystem object once per language, store the content in either a array or a scripting.dictionary object, which I then stored in an application.object variable. My idea was to load each language from the application variable across users sessions. So if UserA loads a page with language 'french' he would load the content of Application.Contents('french_language'), and german in its ovn memory location, english in its own, etc....
I though this would be faster than having each user use a filesystemobject to parse a languagefile for each request.
So my question is: Does anyone know how storing a Scripting.Dictionary-Object in an Application.Object will reduce performance? Will using an regular array be a much faster solution? Will storing a custom class/object work as fast as a regular array, providing the selfmade class doesnt contain any ASP objects itself?
(I though perhaps writing a selfmade class would be better for storing the language and perhaps any related headerinfo).
Thank you for reading!