Hi Zag,

I don't mind disagreements at all. I actually probably need to clarify something. I'm not concerned with the actual javascript code that gets sent out to the client. I'm concerned with the amount of data that gets sent to the client. Also, I may not understand what you mean by javascript connected drop-downs. The javascript that I've used in the past are really very small javascript functions, however, the way that I've used it is that I've had Classic Asp write arrays of data out to the client when the page loads and then the javascript function uses that data on the page to populate the drop-downs. So, all of the data is sent out to the client on the first trip for all of the drop-downs. Its not so bad with two drop-downs but everytime you add a drop-down you're adding another dimension to the array.

So it seems like its a matter of do you want to send out all of the data in one big trip or just send out small amounts of data only when its needed. I have a big, powerful manly server. Still, I don't want to overtax it needlessly. But, I'd rather send out only small amounts of data when its needed.

Unless I'm just not understanding what type of javascript code you're using. If you have some javascript code that will only populate the second drop-down when its needed without making a trip to the server I'd be interested.

Kind regards,
Richard

well Ruchard, you do have a strong point :) but it's all depend on the application it self, I mean, if the user will only choose once or twice from the first drop down list, then the postback solution is much better, but if the user is going to work a lot on that page, there is a lot of server trips, then javascript is better, although I really believe the AJAX approuch is betten than both solutions, less date, less using of the network, easy to implement.. I love it :)

Nothing is impossible. The impossible only takes longer. "Digital Fortress, Dan Brown"

Alaa,

I can see both sides of this issue. I'm just so grateful that I don't have to rely on the javascript. Double drop-downs weren't really so bad but for every drop-down you needed to add the code became incredibly complicated.

I absolutely love the ease of the connected autopostback, on selectedindexchanged, drop-downs in .NET. I have been wanting to get into AJAX, especially what you say about being easy to implement. Is that a .NET 2.0 only functionality? I was wondering if you could point me in the right direction to get started with AJAX??

Thanks,
Richard

Well Richard,

AJAX is really an interesting field to study, I really did not get into it in depth, but I found a ready made assembly for the .NET which has all the major web controls made in AJAX, and it's free to use, Its called "Anthem", it's easy to use and it could really help you in your web application :)
So I really do recommend using it.

(But that if you want to use AJAX, not to learn how to write a code using the AJAX approach :)


Nothing is impossible. The impossible only takes longer. "Digital Fortress, Dan Brown"

hi there..

why using a third party AJAX framework when microsoft has launched an official AJAX framework??

HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from dparsons signature and he Took that from planoie's profile
================================================== =========
My programs achieved a new certification (can you say the same?):
WORKS ON MY MACHINE
http://www.codinghorror.com/blog/archives/000818.html
================================================== =========

They did!!!!!

I really did not know that!!!!!!! :)

tnx mate

Nothing is impossible. The impossible only takes longer. "Digital Fortress, Dan Brown"

Does the official AJAX framework run in .NET 1.1? I understand that it only runs in 2.0. The Anthem project will run in 1.1.

I agree that Ajax will give you the best user experience here and although its quite easy to plug in the Ajax structure, it can be a pain putting together the JavaScript to repopulate your elements with the data tou get back. I use it sometimes (I'm expecting great things from Atlas in 2.0) but sometimes its simpler to hang a little JavaScript event that will display a please-wait image and (as long as the javascript returns true) let your postback happen too.

Haven't heard of Atlas.

If you're going to be posting back to the server anyway, then why not just use the autopostback in .NET? It doesn't require any Javascript. For me its usually a small amount of data on the post back anyway, just the elements that relate to the selection made in the previous drop-down. Jeez, clicking on a link to a new page is a post to the server too. I'm all for performance enhancement.

The Javascript I used to use for multiple drop-downs didn't need to post back to the server because all of the data was written to the page in Javascript array. Working with it a lot, I got pretty good at using it. But triple drop-downs were really a pain.

atlas was the codename for the actual Ajax that's goes into .net 2.0 framework...

HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from dparsons signature and he Took that from planoie's profile
================================================== =========
My programs achieved a new certification (can you say the same?):
WORKS ON MY MACHINE
http://www.codinghorror.com/blog/archives/000818.html
================================================== =========