Damn introduction
Every damn thing has an introduction. Here is my Damn introduction. Future posts in this blog will cover the bolded items of the following in detail. So, read, write back if you have any queries else, stay tuned for more…
I do not intend to cover ASP.NET 2.0 here. It deserves its own blog and it is on the way.
So far, in almost all the cases, a web application involves. I am ignoring the static html websites.
- Reading Data from a Database and Showing it to user in the browser
- Updating the Database by collecting data from the browser
Yes, it is that simple. If you know the above, you sure can say, you know 80% of the skill required to create a web application. Digging one layer further, in almost all the cases, the following would be required. Not all websites are created for everyone’s use unlike Google.com. So, the following two controls the accessibility.
- Authentication: Allow only specific set of users, say employees, to use your website.
- Authorization: Once a user is authenticated, perform one more layer of control. Not every page in the website is for every employee. There may be HR pages that should be accessible to only HR guys. So, control based on the user profile.
- State Maintenance: As we all know, web operates in a stateless environment, where the connection between the user computer and webserver is lost the moment a response is sent to user’s computer by the web server. So, there arises a need for something called “Session Maintenance”. After all we don’t want users to login in each of the pages nor, we want them to have a pen & paper to write down list of items they are willing to buy on the website as they navigate through different webpages.
Just that’s it. Ya. Thatz all. Those are minimum things required. However, there are other things that would come into picture depending how big your application is. - Encryption: Encoding all the contents of a request and response so that no body on the internet can view our data. We use SSL for that.
- Multi-tiering : If there is lot of processing to be done for each request on the webserver, may it is worth doing some of the processing in a different computer. Often referred to as “App Server”. By sharing the load, WebServer will have enough capacity to accept new request and make the website available all the time. So, one has to know “Remoting” techniques to be able to make their application Multi-tier. Web-Service is popular “Remoting” techniques.
- Logging & Error Handling: Mistake do happen. People may try to divide a number by zero. That doesn’t mean the website crash or show unpleasant error to user ? So, warn the user where necessary and keep a log of the error encountered. Error happen for variety reasons. May be database server is down or busy. So, write these unpleasant events in to a log and it will be easy to know at the end of the day of the error.
- Performance Testing / Load Testing: Before you release your website, do a load testing so to make sure it will with stand when the maximum traffic hits your site.
Client side error handling: Javascript is needed to do this. Useful uses would be forcing user to enter data in all the fields, validating email id for its format, may be validating date. We can do all this in the user computer instead of sending all the way to webserver to figure out that the user didn’t enter correct details. - IIS
- Traffic tracking
- Code publishing
- Content Publishing
- Health Monitoring
Stay tuned.
About Me
- Mallik Reddy
- Seattle
- View My Profile
0 Comments:
Post a Comment
<< Home