upper limit to Session variables?

[Amy]

Is there an upper limit to how many Session variables you can
transfer? I'm working on a utility application that passes info from
a web form into a pdf. There's no database access, so I'm using
Session variables, but it's going to end up being a lot of data. Is
this the best way to do it, or is there a better way?

--Amy

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

I don't think that there are a hard limit, it's limited to the amount of
memory and the performance overload of search in the collection. The more
variables you have the slower it may get to locate them in the collection.

Of how many variables are you talking about?

It's possible to instead of having individual variables you could group them
in classes, like each HTML form is represented by an instance?

cheers,

 

[Amy]

On Fri, 28 Oct 2005 13:55:54 -0400, "Ignacio Machin \( .NET/ C# MVP
\)" <ignacio.machin AT dot.state.fl.us> wrote:

The variables are all coming from one form - I'm not sure how grouping
them in a class would help - can you expound on that?

There are about 80 fields in the form, almost all strings. They won't
all be filled out, though.

--Amy

 

[Ken Linder (KC7RAD)]

Amy,

80 fields in the Session should pose no problem. Some of our web apps
handle >100 with no problems. We did discover that using ViewState
does help a bit if you only need to keep data within the scope of a
single page.

Ken Linder
(KC7RAD)