server controls vs traditional

[rbutch]

guys im building an application, that franky is pretty huge when it comes to controls.
about 320 total dropdown list boxes will be populating the same amt of textboxes.
and going to the server really isnt necessary until it's time to write to the database.

my question is, for performance, would it be better to leave these as non <asp:net/>
controls to reduce the constant roundtrips.

i basically built 1/10 of the application using all server controls and it worked excellent, but now that ive expanded it to accomodate 10 employees rather than one, i can see a noticeable difference.

im on a T3 at work, so, im sure im getting the best response vs some of the employess in the field across the US, that most likely would be using this app on a much less powerful pipe.
any feedback is appreciated.

thanks again
rik

**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

 

[Guest]

Rik,

What do you mean by "constant roundtrips"? Are you doing autopostbacks each
time they select from a list? If not, there shouldn't be that big a
difference. The controls are rendered to the client the same way regardless,
and that they're server controls means mostly that the server can handle
events for them (in addition to some other overhead), but there shouldn't be
that many. If all the entries are coming from listboxes I would guess there's
not much validation that has to happen either.

320 controls is a lot, server or otherwise, and if there's a long list in
each one then that's a ton of data for your web server to serve up
regardless. Rather than look at the bandwidth, you might look at server ram,
and presuming the source for your listboxes is the same across users, you
might also use the application cache.

hth,

Bill

 

[rbutch]

hey bill, yes that's exactly what its doing. each dropdown box is set to autopostback to immediately populate the textboxes.
and i was reading about application cache and maybe that's the ticket to the whole thing.
im not an old classic asp coder like much of the rest of the world. i was in oracle and just got into vb.net last summer and now of course asp.net, so it's all new to me.
thanks again for your suggestions and response
rik

**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

 

[Kevin Spencer]

my question is, for performance, would it be better to leave these as non

<asp:net/>
controls to reduce the constant roundtrips.

No. ASP.Net is object-oriented, and every scrap of HTML on the client is
generated by server controls, even literal HTML. You should definitely
optimize your code as much as possible, but not by breaking the model.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.