----- Original Message ----- From: "Simon DeMonfort" <[EMAIL PROTECTED]> Sent: Thursday, April 11, 2002 7:16 AM Subject: .Net Application Architecture
> There seems to be two different ways to architect a .Net web application. I > can either use .Net's OO features and build a glorious object model and > sacrifice speed. If I do want speed then I must comprimise my OO design > principals (ie. encapsulation) and pass my objects around as strings. What > is everyone else doing ? Can anyone point to any good white papers on the > subject. Objects arent inefficient per-se. Object creation and destruction can take time, but strings are just objects themselves. I wouldnt do a glorious object model for the sake of it, checking off every pattern in the GOF book, but I wouldnt seek performance over a maintainable design. Better to get something working fast then profile it -steve You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
