4444Exposing Web Serviceshttp://www.stardeveloper.com/comments/b-071401-1.shtmlWeb Services, in theory, aren't a new concept. They allow distributed applications to share business logic over a network. For example, the classic Web Service scenario is a stock quote service: one company provides a service that can accept requests for stock symbols and respond with stock quote details.ASP.NET > Tips and TutorialsOct 10, 2006
Security is an important attribute of any ASP.NET application. The authentication and authorization of users and resistance against the malicious attacks are important tasks in web applications. In ASP.NET 1.x introduced new authentication service called Forms-based authentication which involves authenticating users and redirecting unauthenticated users again to Login page.
One of the challenges we had was being able to process a PagePostBack and save several hundred records across multiple tables within a reasonable amount of time. Plus, as the tool obtained more and more users with the number of analysis models growing exponentionally, it wouldn't be long before the wait time for data updates became unacceptable. We originally started out by following standard practices for populating classes, calling class methods with these classes as parameters which called stored procedures to save the data points one by one. To enhance performance a bit, we shared an open connection across all of the method calls. On larger models this resulted in waiting 15 seconds or so for the page to post to itself. Not a horrible wait time but I wanted to do better.
Mostly we want to change output results of our applications to another culture setting. In this code sniplet we will format current date time for our culture settings
In the last article, I explained the basics of supporting mobile devices in ASP.NET. After reading that article, I hope you would have grasp the basics of writing mobile pages and using mobile controls for developing mobile specific web sites
Let's also review the application environment. A typical user analysis model would consist of around a 100 of these data entry pages. The Web site itself supports an unlimited number of analysis models. Thus, the database is quite large and the process of obtaining the meta data is quite complex. Running more queries than absolutely necessary can be a real drag on performance. Also keep in mind that a typical user will spend anywhere from 15 - 45 minutes on a single data entry page completing that section of the analysis model.
Normally, I would be reluctant to implement a solution that loads up the ViewState in this manner. Our web farm environment pretty much ruled out the use of static objects or the application cache. The performance impact of having larger than normal ViewState and the process of managing ViewState isn't necessarily prohibitive. That said, if you are trying to squeeze out every once of performance, doing this without it being necessary could hurt your cause.
You can use my sample as a means to measure how much is being stored in ViewState for the amount of data you expect to have in your own application. The default setting of 60 textboxes and 60 dropdown lists (each list contains 10 records) takes up roughly 100KB of html and ViewState combined
Joining mailing list will entitle you
to receive occasional emails informing you of news and
updates to the site and any special offers that may be
of interest to you.