Posts Tagged ‘Web Technology’

What is jQuery ?

August 20, 2011 Leave a comment

jQuery is great library for developing ajax based application. jQuery is great library for the JavaScript programmers, which simplifies the development of web 2.0 applications. You can use jQuery to develop cool web 2.0 applications. jQuery helps the programmers to keep code simple and concise. The jQuery library is designed to keep the things very simple and reusable.

jQuery library simplifies the process of traversal of HTML DOM tree. You can use jQuery to handle events, perform animation, and add the ajax support into your web applications with ease.

Why jQuery?

You can use simple JavaScript to perform all the functions that jQuery provides. Then why jQuery? The jQuery library is providing many easy to use functions and methods to make rich applications. These functions are very easy to learn and even a designer can learn it fast. Due to these features jQuery is very popular and in high demand among the developers. You can use jQuery in all the web based applications irrespective of the technology.

jQuery is java script and can be used with JSP, Servlets, ASP, PHP, CGI and almost all the web programming languages.

The jQuery code is very simple and easy to learn.

Here are the features of jQuery

  • DOM element selections functions
  • DOM traversal and modification
  • Events
  • CSS manipulation
  • Effects and animations
  • Ajax
  • Extensibility
  • Utilities – such as browser version and the each function.
  • JavaScript Plugins

How much time is required to learn jQuery?

You can learn jQuery in a day and master it within 2-3 days. There are so many features available with jQuery and you may spend months to explore these features.

We have spent huge time in exploring the jQuery and developing almost all the examples that can be developed with jQuery. So, explore our huge collection of jQuery tutorials and examples. Please continue reading the tutorials.

Ref :


Dual MVC

August 17, 2011 Leave a comment

Dual MVC contains both, Push MVC and Pull MVP design pattern. that is why it is called Dual MVC design pattern.

  • The push-style MVC, (Model View Controller or MVC), which is the classic design pattern which decouples data access and business logic (model) from presentation layer (view) by introducing an intermediate component: the controller.
  • The pull-style MVC, (Model View Presenter or MVP), where the view is able to “pull” data from multiple controllers as needed. This approach eases the creation of rich web user interfaces.

For a better understanding of both patterns, let say that MVC is the piece in charge of executing the logic to show a page while MVP is the piece in charge of executing the logic associated to the page UI (i.e. the logic that is executed when the user click on a button or select an option from a drop-down list).

Authentication & Authorization

August 5, 2011 1 comment

It is easy to confuse the mechanism of authentication with that of authorization. In many host-based systems (and even some client/server systems), the two mechanisms are performed by the same physical hardware and, in some cases, the same software.It is important to draw the distinction between these two mechanisms, however, since they can (and, one might argue, should) be performed by separate systems. What, then, distinguishes these two mechanisms from one another?

Authentication is the mechanism whereby systems may securely identify their users. Authentication systems provide an answers of the following questions:

  • Who is the user?
  • Is the user really who he/she represents himself to be?

An authentication system may be as simple and insecure as a plain-text password challenging system as found in some older PC-based FTP servers or as complicated as the Kerberos system described elsewhere in these documents. In all cases, authentication systems depend on some unique bit of information known or available only to the individual being authenticated and the authentication system — a shared secret. Such information may be a classical password, some physical property of the individual fingerprint, retinal vascularization pattern, etc., or some derived data as in the case of so-called smartcard systems. In order to verify the identity of a user, the authenticating system typically challenges the user to provide his unique information (his password, fingerprint, etc.) — if the authenticating system can verify that the shared secret was presented correctly, the user is considered authenticated.

Authorization, by contrast, is the mechanism by which a system determines what level of access a particular authenticated user should have to secured resources controlled by the system. For example, a database management system might be designed so as to provide certain specified individuals with the ability to retrieve information from a database but not the ability to change data stored in the datbase, while giving other individuals the ability to change data. Authorization systems provide answers of the following questions:

  • Is user X authorized to access resource D?
  • Is user X authorized to perform operation J?
  • Is user X authorized to perform operation D on resource J?

Authentication and authorization are somewhat tightly-coupled mechanisms — authorization systems depend on secure authentication systems to ensure that users are who they claim to be and thus prevent unauthorized users from gaining access to secured resources.

Figure I, below, graphically depicts the interactions between arbitrary authentication and authorization systems and a typical client/server application.

Authentication vs. Authorization