Portlets ....why ? (part 1)

AGENDA

• Traditional Web Application
• Shortcomings of traditional Web Application
• What is needed?
• What are Portlets? Portals?....
• The New Generation answer …..


Traditional Web Application

• The “W W W” --The world wide web ,subset of internet is responsible for information sharing.

• The Website Approach ---each application is developed separately like a website and deployed singly on a server.

• The Client Server --the usual client server architecture involves synchronous request response paradigm.

• The Users' Perspective --the user access the website ,using the browser and can work with a single website at a time.A single application to interact with.A single repository of information.

• The Developers' Perspective --separation of work and single handed workaround with no plug and play feature.A huge effort is required to maintain,re-engineer or add a new application to an existing one.

• The Business ….Market….Bottom-line -- a huge cost incurred as the project is nearly developed from scratch (or even if component reuse ).In these hard times market and bottom line are the deciding factors for the fate of the project,people and even the company.

Traditional Web Application -Drawbacks

• Lack of Personalized Matter --the content is hard to personalize,lack of personalized matter means lack of edge on the business for traditional web application.

• Segregated Approach --the development is done in separation,a foreign developer body cant collaborate and no plug and play features included,developed by an external developer.

• Difficult for technology up gradation --a technology update in an existing web application is difficult to inherit.

• Single Handed Approach --a traditional web application is developed singlehandedly by a certain community of users and are deployed on a web/application server with no specific way to incremental upgradation.

• Difficult to Maintain --as the development goes on and one it becomes very hard to maintain and at a time the entire application can collapse for a simple and difficult to trace fault.

• Difficult to Re-engineer --very difficult to re-engineer and maintain stuff.

• Separate User Management --the entire user management is separately developed and no inbuilt support is given by the web server.

We Need…..

• Personalized Matter
• Integrated Approach….
• Ease of technology Upgradation….
• Community and collaboration framework ……
• Application Repository……
• Easy to Re-engineer…….
• Painless User Management….
• Hassel Free Maintenance

What are Portlets? Portals?....






















What did u understand from the above image. Look closely at the image and u can find that each and every application is associated with a portlet window which can be minimized , maximized, closed or removed form the portal page . It means that each and every portlet is a small application which can be arranged on the portal page as we like and also it has inbuilt support of personalization and user management.The entire thing is asynchronous also also conforms to web2.0.....its like magic!
a close look at the skeleton of a portal page along with portlets which show contents called fragments











The New Generation answer ….. what is the new generation answer to the drawbacks of traditional web applications its Portlets and Portals..