It's not that caching doesn't work on web farms, it's just that you have to be careful about what you cache.
Assuming you are not updating the cities (there are no new states on the horizon as far as I know), go ahead and cache the data -- it can't get out of synch. The only reason you don't want to cache application data in a web farm is when the users can update that data. For static data this is not an issue. On 9/21/05, sindarintech <[EMAIL PROTECTED]> wrote: > I have pair of dropdown lists that get retrieved fairly often... > they're related in that the one on the left determines what's > displayed in the one on the right. For example, 'states' on the left > and 'cities' for the selected state on the right. > > The application will be located on a web farm and I'm under the > impression that caching isn't an option because of the web farm > architecture. (Please tell me if this is incorrect!) > > We also do not have access to a state server. > > The problematic part is that a user is allowed to insert rows into a > grid and that each row contains an instance of the dropdowns. As the > rows increase, so does the size of the viewstate. > > Is there a better way to do this using OO? > > Thanks in advance! > Ray > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > -- Dean Fiala Very Practical Software, Inc http://www.vpsw.com ------------------------ Yahoo! Groups Sponsor --------------------~--> Fair play? Video games influencing politics. Click and talk back! http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/saFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
