|
Subject:
|
Does Repeater put a strain on server?
|
|
Posted By:
|
MichaelTJ
|
Post Date:
|
10/24/2003 6:45:13 PM
|
I'm wondering about something. When I used ASP I got an advice from a tutor. He said to be carefull not to use too many <%%> inside my code because it put a strain on the server.
I'm now started using ASP.NET, and I've played around with repeaters. And I'm looking at all these <%%> inside a repeter.. does it put an unessecary strain on the server copared to make some if.. ..then response.write("<P> this text " & strVar & " is a text") in code behind instead???
Any thoughts?
------------------------
All help is Good help!
Regards
Michael
|
|
Reply By:
|
planoie
|
Reply Date:
|
10/27/2003 11:06:47 AM
|
I think you are safe to use those in your ASP.Net ASPX files as the examples for the repeater controls do. Although it probably does put more strain on the server than not using them at all, it should do much harm. Depending on what you are trying to acheive with your repeater control, you might be able to use some other controls that are better suited (like the datagrid or datalist controls).
Peter
|
|
Reply By:
|
MichaelTJ
|
Reply Date:
|
10/27/2003 11:46:48 AM
|
Thanx for replying Peter.. I was mainly wondering because some of my site will eventually have 4k - 6k rows. And I thought that a repeater that loops through these and making 4 to 8 <%%> pr. row will strain the server quite much. But then I found a sample code on how to make typical Next Page, Previous Page work with repeater, so now it's not too bad (50 rows pr page only).
------------------------
All help is Good help!
Regards
Michael
|
