hey all,
i have a datatable that i'm keeping in application state only to be used by
my datalayer class. i have to cast it from my code-behind and pass it to my
datalayer on each postback.

any suggestions on how to improve this type of overhead? is the answer going
to be to design it differently?

thanks,
rodchar

rodchar,

I wouldn't worry about it. If you are just casting the data table, its
a trivial operation, with virtually no performance overhead. If you were
running this in a tight loop many, many times, I'd understand, but that
doesn't seem to be the case.

That's assuming you are storing session state in memory. Is that the
case?

--
- Nicholas Paldino [.NET/C# MVP]
- (E-Mail Removed)

"rodchar" <(E-Mail Removed)> wrote in message
news:5CEC2EEC-544B-4730-BABF-(E-Mail Removed)...
> hey all,
> i have a datatable that i'm keeping in application state only to be used
> by
> my datalayer class. i have to cast it from my code-behind and pass it to
> my
> datalayer on each postback.
>
> any suggestions on how to improve this type of overhead? is the answer
> going
> to be to design it differently?
>
> thanks,
> rodchar

I wouldnt worried about this till u start rendering your datatable in grids.
In this case suppose to use simplified storage, like custom collections or
json.

--
WBR, Michael Nemtsev [C# MVP].
Blog: http://spaces.live.com/laflour



"rodchar" wrote:

> hey all,
> i have a datatable that i'm keeping in application state only to be used by
> my datalayer class. i have to cast it from my code-behind and pass it to my
> datalayer on each postback.
>
> any suggestions on how to improve this type of overhead? is the answer going
> to be to design it differently?
>
> thanks,
> rodchar