Caching and encapsulating data and presentation in UserControls (and then caching them) are 2 ways to make an app faster. Clever Library design is way to make apps more maintainable.
http://learnasp.com/freebook/learn/vb_firstlib.aspx for library basics or the C# version at http://learnasp.com/freebook/learn/cs_firstlib.aspx User Control examples abound @ http://learnasp.com/freebook/learn/ including examples where caching makes it 1000 x faster either data caching or fragment caching. http://www.learnasp.com/ub is the ultimate example of a library reducing code size and simplifying code. On 6/2/05, Tony Trapp <[EMAIL PROTECTED]> wrote: > Hi Charles that makes perfect sense of course speaking directly I > think is always best I am revamping a web app for maximum speed and > execution and anything to make very powerful is the way to go. > > Its already seems when my page executes it just pops in like a snap. > > Is there any other way to make a web app more powerful? > > already using stored prcedure and of course now sql conn not oledb > > uisng win 2003 server with http compression, 2.somthing ghtz > 1.somthing gig ram 100 mps per sec connection. > > Any suggestion? > > Tony... > > > --- In [email protected], Charles > Carroll > <[EMAIL PROTECTED]> wrote: > > SQLClient is lightning fast as it talks straight to something > callled > > SQLServer TDS without OLEDB in the middle. > > > > It is closer to "native access". If there was a System.Data.MSAccess > > library of course using that would be faster than OLEDB to talk to > > Access but at this time there is not. Stepping back from ccomputers > If > > you could speak French to a French person or translate your English > > statement to a Spanish statement and have the Spanish person then > make > > the equivalent French statement it is slow and may lead to less > > quality of translation. > > > > OLEDB can talk to many databases and has fat and inneficiency which > we > > tolerate so we can talk to any database with an OLEDB driver. But we > > oly tolerate it when we have no direct way to talk to the data. > > > > On 6/2/05, Tony Trapp <[EMAIL PROTECTED]> wrote: > > > Hey guys I just wanted to know which is better to use when > connecting > > > to SQL server 2000. > > > > > > OleDb or sqlserver > > > > > > Which one would you choose and why. > > > > > > Thanks guys !! > > > > > > Tony... > > > > > > > > > > > > ________________________________ > > > Yahoo! Groups Links > > > > > > > > > To visit your group on the web, go to: > > > http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ > > > > > > To unsubscribe from this group, send an email to: > > > [EMAIL PROTECTED] > > > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of > Service. > > > > ________________________________ > Yahoo! Groups Links > > > To visit your group on the web, go to: > http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ > > To unsubscribe from this group, send an email to: > [EMAIL PROTECTED] > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
