Loading Data for web application

[sds814]

So far I have learned two ways to load data for dropdown lists and other server controls that is required when starting an application. The first one is to fill a dataset that has all the datatables the stored procedure calls and then sharing that dataset. The other is saving into Cache and then inserting/getting data from the cache. Which one is better? And if there are other ways that you would recommend please provide information.

Thanks

 

[adamroof]

i prefer the datasets and datatables, limiting the db calls, and tuning the sp's.

if the data is not changing that frequently, then i would lean to using cache. My main concern in web apps with cache is who is seeing what data and when. My developments have had to have real time data.

there are cache issues to handle differently, but if you have more users than the average bear, and mostly static data, then, getting those accomplished and implemented might better suit you.

I have had developments done on an intranet, then used the concept and published external sites. I am amazed how fast the db calls and the dot net framework run no matter if the server is in the next room or 3 states over. I do see a difference, but thats only about 1 second per page as opposed to .5s internally.

Keep in mind the rendering too. Have clean and doctype compliant html, try to use tableless designs, and external css files, which cut the file size in half thats downloaded to the users each request.

 

[sds814]

Thanks for the post, Adam.

If you can please explain why it's better to use tableless designs. Usually what I've done is embed server controls in html tables.

And in the 4th paragraph you mentioned that you use the concept and published external sites. Do you mean the concept of binding data to a dataset and then use datatables?

 

[adamroof]

Well, its a can of worms. It is easier to design with tables, and harder to not use them. I wish this wiki was around earlier...

http://en.wikipedia.org/wiki/Tableless_web_design

DIV and SPAN tags can be used to accomplish the layout. But requires alot of fine tuning, especially if you are writing for multiple browsers, and accessibility.

Going back and redesigning html to tableless allowed me to go from 165KB to about 90KB on one file, but it included implementing and external CSS too. Major diff? prolly not, but i did get a "Wow, the page loads so much faster" from about half the users.

You can still use tables, but for data that belongs in a table. What you are doing is fine, it all works, and if the appearance is what you are after, then no need to change.

I bring this up due to your asking about cache, which i assumed you were looking to speed up your pages.

By concept i meant the overall design, which included datasets and no cache, but placed on a hosted server for the outside world with users across the country accessing it everyday.