Server Controls Can't Replace DHTML?

[crazyboybert]

Hi All

This may seem a stupid question, it maybe that i'm missing the point somewhere with this one! I'm working on a couple of dotnet apps at the moment - one is for an intranet and hence trips to the server aren't 'so' important - the other is a small online store aimed at jo public with allsortsof browsers, connections etc...I'm usign server controls all over on the intranet and its making life lots easier. Coming to do the Wibbly Wobbly World site and i start to think a little on efficiency. Using server controls is great for the business logic at the back end but say i have a dropdownlist of product types and an image i want to change when the product change. Having this as a server control using the built in .net events to update an asp:image onchangeselected (or whatever the event is) is going to mean a round trip to the server each time - yes? Im starting to write my own client side script over the top of the .net server controls to provide the client side3 func over the top....

My question then...Is this the best way to do things - can i really not use the server controsl as designed/instructed by M$oft without crippling usability for those on slower connections? Or am I just missing the point somewhere?

Cheers for your thoughts..

Rob )

------------------------------------

Go placidly amidst the noise and haste,
find what peace there may be in silence.
-Anon

------------------------------------

 

[Custom24]

No I don't think you are missing the point. ASP.net provides a much more OO, elegant, efficient and powerful model for server side code but cannot overcome one of the limitations of the internet - that a postback takes time.

One thing you might consider is developing the functionality you want as a custom control or user control so that it can be used again in other pages.



Mark