View Complete Post
I have read online about the disadvantages and advantages of the different application architecture tiers. I try to use an n-tier architecture when I build my web applications, but also build 2 tire applications for quick pushout applications that do not require many forms or logic. I have not read anything dealing with the performance pros and cons of using a specific architecture over another. Wanted to see what members opinions were and which is the best method to use, be it 2-tier, 3-tier or n-tier.
Can anyone explain me the advantages & disadvantages of Microsoft Silverlight?
We will implement a workflow on a item whose duedate may be after 5-6 months. On reached duedate there will some activity perform.
So can I use while loop to check and when duedate reach some logic will be executed.
Duedate is so long. So can anybody light some pros-cons about whie loop? what are the problem I may face in future?
i want to know what are the advantages of transaction log backup in sql server 2008?
what are the advantages of time dimensions over regular dimensions?
the semi-additive aggregation functions won't work w/o a time dimsion?
I´ve created several web pages, that makes use of HTML injection. That means a script on a web page that calls a web service, gets html code returned, and the script then injects the html code in a div somewhere.
This solution avoids postbacks, returns data faster back to the end-user and creates a more smooth web experience.
But what are the downsides of html injection? The only thing I can think of, is that code maintainance gets harder as the project gets larger..
Thanks for your thoughts.