在会话中存储我的自定义类的1000多个实例的列表是否是内存问题？

Question

Is storing a list of 1000 instance of my custom class to the session variable a good approach ? My asp.net web app need multilingual support and i am storing the labels in a table.I will have multiple users who has their own language preference and text(label content) preference.

I am thinking about loading the labels and store it in session variable and access that to use in the pages.Storing it in Application variable does not work because each customer have their own text for the labels.So is storing session a good way of doing this ? I guess i will have almost 1000 labels as of now and it may increase as the application grows.

My custom class has 2 proprties. LanguageCode and LanguageName

for some reason i cant use asp.net Resource files :(

Whats your thoughts on this ?

Answer 1

您应该为每种语言存储一组标签，然后在会话中存储语言名称并使用它来查找正确的标签集。

Answer 2

Some thoughts to notice:

If your managers have something in particular against resx's, you can store all those labels in any other format (eg plain text files), or in a DB.

If you have little amount of users, and loading time is extremely crucial, your managers may have a point. Other than that, they're wrong, and I would consider trying to explain that to them.

Try considering "computing" the labels at runtime (eg if some of them include adding prefixes, suffixes, etc. you can save only the "stems" and provide a relevant label only on demand. That will save you some server space).

Answer 3

如果您是我，那么我将首先花一些时间来弄清楚为什么您的资源文件不起作用...只要您将Thread.CurrentThread.CurrentCulture（或CurrentUICulture？）值设置为特定的区域性，并且将资源文件放置在正确的位置，我想不出任何原因说明为什么它不起作用。

Answer 4

Not a good idea, there are two problems with it:

• It will use up the memory on the server, and reduce the number of users that can use the system
• The time for each request will increase

The standard way to do this is using RESX (resource) files. You should try to fix that.

Answer 5

Why not use Application variable and create as many Application variables as the languages you have. Each application variable will be a superset of all the labels for that language.
Or maybe store the entire table(s) in application variable(s), instead of storing multiple session variables that, I assume, they intersect with each other.