DropDown and Caching

[JJ]

If I were to use Caching for a dropdownlist can I disable viewstate for
this control? Would I lose control behavior like selectedIndex etc.? I
would think since my ddl has like 50+ rows in it and they don't change
once the ddl is populated that this control would be an ideal candidate
for Caching, agreed?

Thanks,

JJ

[Mark Rae]

"JJ" <jj****@hotmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...

If I were to use Caching for a dropdownlist can I disable viewstate for
this control? Would I lose control behavior like selectedIndex etc.?

I would think so...

I would think since my ddl has like 50+ rows in it and they don't change
once the ddl is populated that this control would be an ideal candidate
for Caching, agreed?

If the underlying data never changes or, at least, changes *very*
infrequently, you will gain some (but probably not very much) performance by
caching the DataSource. I quite often do this for static or almost static
data, e.g. countries and currencies - saves a database query every time the
underlying data is required.

[master_programmer]

Use ODBC its easier.

Mark Rae wrote:

"JJ" <jj****@hotmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...

If I were to use Caching for a dropdownlist can I disable viewstate for
this control? Would I lose control behavior like selectedIndex etc.?

I would think so...

I would think since my ddl has like 50+ rows in it and they don't change
once the ddl is populated that this control would be an ideal candidate
for Caching, agreed?

If the underlying data never changes or, at least, changes *very*
infrequently, you will gain some (but probably not very much) performance by
caching the DataSource. I quite often do this for static or almost static
data, e.g. countries and currencies - saves a database query every time the
underlying data is required.