Posted by
Amit
|
Posted in
ADO.NET
|
Posted on
Wednesday, March 17, 2010
ADO.NET internally works with .NET data providers (or .NET data bridge provider) to connect to and access data from different kinds of data sources (including databases). The same data provider model existing in ADO.NET 1.1 is further enhanced in ADO.NET 2.0 (with new factory classes) to leverage the flexibility of developing database-independent applications.
What exactly is a factory class? The purpose of a factory class is to provide an interface for creating families of related objects, with or without specifying their concrete (method implementation) classes. If the factory class is created without one or more implementations of methods, we call it as an abstract factory class.
Posted by
Amit
|
Posted in
ASP.Net
|
Posted on
Wednesday, March 17, 2010
ASP.NET is a powerful platform for building Web applications, that provides a tremendous amount of flexibility and power for building just about any kind of Web application. Most people are familiar only with the high level frameworks like WebForms and WebServices which sit at the very top level of the ASP.NET hierarchy. In this article I’ll describe the lower level aspects of ASP.NET and explain how requests move from Web Server to the ASP.NET runtime and then through the ASP.NET Http Pipeline to process requests.
Posted by
Amit
|
Posted in
Security
|
Posted on
Friday, February 26, 2010
The Secure Sockets Layer (SSL)
The Secure Sockets Layer (SSL) is a protocol that provides secure communication between client and server. Here the client is your browser and server is the web site you're communicating with. Secure communication has three main goals: privacy, message integrity, and authentication.
Posted by
Amit
|
Posted in
RDBMS
|
Posted on
Friday, February 26, 2010
The Waiting ... Is the Hardest Part
Please wait ... and wait and wait again. One of the nagging problems many databases can't seem to shake is that at some point a user is going to have to wait while someone else updates the system. Whether the database system is using table-level, page-level, column-level, or row-level locking, the same problem arises: readers (SELECTs) wait for writers (UPDATEs) to finish, and writers (UPDATEs) wait for readers (SELECTs) to finish.
PostgreSQL, the open source database that is often compared to most advanced commercial databases, has a mechanism called MVCC (MultiVersion Concurrency Control). MVCC has the ability to perform row-level locking as well as lock rows for writing in one session while giving access to these rows unaffected in another session. It's been said that MySQL, a lightweight open source database, has a version of MVCC, but the two aren't really comparable since MySQL can do only table locking for reading. This is one of the many instances where PostgreSQL has the upper hand.
Posted by
Amit
|
Posted in
RDBMS
|
Posted on
Friday, February 26, 2010
This document answers the question that some clients ask: "Why use PostgreSQL (as opposed to MySQL, Oracle, MS-Access, FoxPro, etc.) for web application development?"PostgreSQL is a Relational Database Management System (RDBMS) that Summersault prefers as the back-end data management component for the database driven websites that we develop. As there are other popular choices available, it's good to clarify why we make that particular choice.
It's worth noting right away that the choice of RDBMS is often highly dependent on the parameters and requirements of an individual project. So while we express our preference of PostgreSQL here for the typical project, we in no way mean to imply that PostgreSQL is the right choice for every project.
Posted by
Amit
|
Posted in
RDBMS
|
Posted on
Friday, February 26, 2010
This article compare general and technical information for a number of Relational Database Management Systems.
Posted by
Amit
|
Posted in
ASP.Net
|
Posted on
Tuesday, January 26, 2010
It can hardly be said that any serious programmer has had to deal with database programming at least some time in their careers. So it would be logical then to make sure your code to these underlying databases are as efficient as possible. Hopefully I will share some of the best practices. These techniques were learned from a variety of sources. Hopefully you will find them equally as useful as I do.
