IBM WebSphere Application Server - WAS

IBM WebSphere Application Server (WAS), a software application server, is the flagship product within IBM's WebSphere brand. It was initially created by Donald Ferguson,
 who later became CTO of CA Technologies, and the first version was launched in 1998.

  ++++>  An application server that can go from single server to a moderately sized configurations or to a dynamic web applications requiring web tier clustering and fail over across multiple application server instances.

   ++++>   WebSphere Application Server offers valuable options for a fast and flexible Java application server runtime environment and enhanced reliability and resiliency.

   ++++>   In World wide top 7 Banks out of 10 are using IBM WebSphere for there Server.


                          ...........DOWNLOAD IBM WebSphere application server from below link.........

                                                 "Click here for DOWNLOAD"

PGEC/PGECET 2012 Phase-2 Seat Allotments..,

PGECET web options entry is over, 

now all candidates waiting for PGECET 2012 seat allotments.

And a good news for students who didn't get seat in Phase-1.

(@)  In A.P total 24941 seats are available for M.Tech

After Phase-1 total 17772 seats are available.  

(@)  In A.P total 11200 seats are available for M.Pharmacy

After Phase-1 total 6913 seats are available.  

For Allotment details click below link..,

http://www.pgecet.apsche.ac.in/

For College wise allotment details click below link ..,

http://www.pgecet.apsche.ac.in/colallotform.php

@ All the Best @

Collection Frame Work in Java

collection framework in java

The collections framework was designed to meet several goals.

1. The framework had to be high-performance. The implementations for the fundamental collections (dynamic arrays, linked lists, trees, and hash tables) are highly efficient.
2. The framework had to allow different types of collections to work in a similar manner and with a high degree of interoperability.
3. Extending and/or adapting a collection had to be easy.

Toward this end, the entire collections framework is designed around a set of standard interfaces. Several standard implementations such as LinkedList, HashSet, and TreeSet, of these interfaces are provided that you may use as-is and you may also implement your own collection, if you choose.

A collections framework is a unified architecture for representing and manipulating collections. All collections frameworks contain the following:

1. Interfaces: These are abstract data types that represent collections. Interfaces allow collections to be manipulated independently of the details of their representation. In object-oriented languages, interfaces generally form a hierarchy.
2. Implementations i.e. Classes: These are the concrete implementations of the collection interfaces. In essence, they are reusable data structures.
3. Algorithms: These are the methods that perform useful computations, such as searching and sorting, on objects that implement collection interfaces. The algorithms are said to be polymorphic: that is, the same method can be used on many different implementations of the appropriate collection interface.

In addition to collections, the framework defines several map interfaces and classes. Maps store key/value pairs. Although maps are not collections in the proper use of the term, but they are fully integrated with collections.