Archive for the ‘Concepts’ Category

Page 3 of 3123




Why Sybase is similar to Microsoft’s SQL Server

Posted on May 13th, 2007 in Concepts | 1 Comment »

Recently I got the opportunity to have a look at the Sybase DBMS and while reading through some of the material on it I had this thing in my mind constantly picking up the tit-bits from where I had left Microsoft’s SQL Server a few months back. It seemed so similar.

Other Sybase beginners might have a similar gut feeling that Sybase is so MS SQL server alike. If you are a Sybase first timer, it would be a matter of surprise and a matter of pleasure to hear than the base architecture of Sybase and MS SQL Server is the same! This means you don’t have to learn new concepts like when introduced to a new DBMS, like Oracle, which has an entirley different DBMS behavior than most of its counterparts. The enlighment I got from searching over the net was the following article, which makes it clear why the Sybase concepts are very much equivalent to those of Microsoft’s SQL Server.
Read the rest of this entry »

Inversion of Control – for easy integration

Posted on April 23rd, 2007 in Concepts, Java, Java EE | 3 Comments »

You may have witnessed some of the J2EE frameworks provide a technique to get dynamically bound plain objects by making them bind to some features of the framework outside of the plain objects. This technique is called as the IoC or Inversion of Control. If we have to know about the meaning of this term let us emphasize on what inversion depicts in aspect of implementing some features in plain objects.

Overview
Suppose I have some functionality of my J2EE application in my model which is nothing but a simple POJO. Now I want this POJO to be incorporated into a web tier which is an MVC (Model View Controller) Architecture. The last thing I would want to do is modify the source of the model, view or controller and put in some additional code which would do this integration. But suppose I choose a framework in such a way that I put what exactly is to be done by the POJO in the MVC architecture in a simple XML config file and then put the config file in the framework and the framework does the rest of the integration work. Read the rest of this entry »

Optimal use of Ajax – use Ajax the smart way

Posted on April 10th, 2007 in Ajax, Concepts, JavaScript | 3 Comments »

Web 2.0 is the thing that can make your site stand out from the hoard of web sites springing up day by day. But are they efficient enough to make a big impression? You need to analyze on some common principles to make the best impression. These principles make you use it in the smart way! Web 2.0 today dominates mostly in the usage of Ajax today. I had written on how to go about choosing the right framework and the different types of frameworks which are available to you to join the web 2.0 league. Today let’s see how can you can use Web 2.0 features in the smart manner because the smartness will inspire others to work efficiently as well.

Looking at the features of Ajax that hundreds of frameworks today provide, you might get sometimes tempted to use them all. Its pleasing when the user interface is more interactive and more user friendly at the same time attractive. To make these you have to use the framework which provides such eye candy. But before you decide on a particular you must have these things in mind.

  1. Size of the total number of JavaScript pages
  2. Check for frameworks or API for memory leaks
  3. Don’t bloat your code
  4. Use interactivity only where required
  5. Don’t try to use Ajax where bookmarking is heavily used
  6. Test your Ajax code properly

Let’s see each one in detail. Read the rest of this entry »

Development and Deployment Structures – the perfect way to build a web application

Posted on March 31st, 2007 in Concepts, Java EE | 10 Comments »

It is always beneficial to have a development and a deployment structure when building an application. It is a perfect way to build a web application. First of all let’s see what is the difference between them.

Development Structure
It is the structure or hierarchy of files that you make in order to make a separation of content based on factors like

  • project modules – every module has its own folder structure
  • repository policy – your company might follow some standardized hiearchical pattern for versioning
  • separation of source code from compiled one – they must not be mixed anytime
  • separation of tiers in the application – each tier might use different components so they better remain separated

An example for the development structure might be as follows:

Read the rest of this entry »

Page 3 of 3123