I am a new comer to web design as well as for my first project I need to have 4 cascading down drop lower menus. Ive been reading through around I'm able to about the easiest method to tackle this and there's some discussion about whether or not to preload these lists in order to grab them from the database. Mine is really a Light project and that i have about 5000 products that will need to go in to these dropdown menus. The discussion I have seen states that without having a lot of dropdown products you're much best preloading these products and tugging them using javascript. My real question is what's considered a significant number? With 5000 products shall we be held much best going the MySQL route? On some level I favor that but all the lessons available appear to cope with either ASP or preloaded products. So my questions are:

Is 5000 products a lot of to preload for any dropdown list? An amount the cutoff be?

And, are you aware associated with a good lessons to obtain me began if MySQL is what you want. I have seen a few but they're not so detailed as well as for a new I am getting wrapped round the axle. Thanks a lot!

To begin with, 5K in dropdowns, not a way! Same for caching it in JS. My advice could be, attempt to investigate PHP, AJAX and MySQL. Then create an autocomplete system that enables for any non-mindblowing approach to access the data.

Should you still require a good tutorial or PHP MySQL dropdowns: http://www.yourwebskills.com/mysqldropdown.php

As well as my advice:

http://beski.wordpress.com/2009/11/20/jquery-php-mysql-ajax-autocomplete/ http://www.webinone.internet/lessons/php/auto-complete-text-box-with-php-jquery-and-mysql/

Please read around, and when you cannot figure stuff out, please return and request!

I'd look more towards the size in kb than the number of products. I am speculating even 5k records will probably be 1-2kb after gzip, that is generally hardly any in comparison towards the relaxation from the exterior objects an average web page loads(rival how big images + css + js).

Needing to do multiple separate http demands is costly from the responsiveness perspective, specifically for high latency connections like mobile products(web autocomplete is usually pretty lame on my cell phone because of latency).

So anyway, personally I lean heavily towards just loading everything upfront unless of course the quantity of data will get huge, or the risk of the information getting used whatsoever is extremely low.