tag:blogger.com,1999:blog-370665582011-11-27T17:37:16.154-08:00Amit Ranjanhttp://www.blogger.com/profile/08501750120817164659noreply@blogger.comBlogger21100tag:blogger.com,1999:blog-37066558.post-22464014831185345652007-03-28T05:40:00.000-07:002010-04-23T04:07:33.863-07:00<ul><li><u>Group of objects are handled using collection framework.</u></li><li>It allows different type of collections (dynamic arryas, Linked List, Trees and hash tables) to work <u>in a similar manner with interoperability.</u></li><li>Some partial implementations are provided to <u>create own collection.</u></li><li>Several implementations (such as LinkedList, HashSet and TreeSet) are provided to use.</li><li>Mechanisms were added that allow the integration of standard arrays into the collection framework.</li><br /><script type="text/javascript"><!--<br />google_ad_client = "pub-4068200296392764";<br />/* 728x15, created 4/23/10 */<br />google_ad_slot = "9774808589";<br />google_ad_width = 728;<br />google_ad_height = 15;<br />//--><br /></script><br /><script type="text/javascript"<br />src="http://pagead2.googlesyndication.com/pagead/show_ads.js"><br /></script><br /><br /><br /><li>A interface <u>Iterator</u> is created by collection framework which provides a means of enumerating the contents of collection.</li><li>Since each collection implements <u>Iterator</u>, the elements of collection class can be accessed through the methods defined by <u>Iterator.</u></li><li>In addition to collections, the framework defines several Map interfaces and classes.</li><li>Maps store key/value pairs.</li><li>Maps are not collection but a collection-view of a map can be obtained and thus contents of a map can be accessed as collection.</li></ul><p>The collection framework defines following Interfaces:</p><ol><li>Collection Top of the collection hierarchy.</li><li>List Extends Collection to handle sequnces (lists of objects)</li><li>Set Extends Collection to handle sets (contain unique elements)</li><li>SortedSet Extends Set to handle sorted sets.</li></ol><ul><li>Collections that supports the methods which enable to modify the contents of it are called <u>modifiable</u> otherwise <u>unmodifiable</u>.</li><li>If such method is applied to unmodifiable collection, an UnsupportedOperationException is thrown.</li><li>All the build-in collections are modifiable.</li><li>If a collection can't be modified then <u>UnsupportedOperationException</u> is thrown and <u>a ClassCastException is generated when one object is incompatible object to a collection.</u></li></ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/37066558-2246401483118534565?l=compu-sc.blogspot.com' alt='' /></div>Amit Ranjanhttp://www.blogger.com/profile/08501750120817164659noreply@blogger.com0tag:blogger.com,1999:blog-37066558.post-1162560874113072022006-11-03T05:21:00.000-08:002006-11-03T05:34:34.123-08:00<div align="justify"><span style="color:#660000;">Client/server describes the relationship between two computer programs in which one program, the client, makes a service request from another program, the server, which fulfills the request. Although the client/server idea can be used by programs within a single computer, it is a more important idea in a network. In a network, the client/server model provides a convenient way to interconnect programs that are distributed efficiently across different locations. Computer transactions using the client/server model are very common. For example, to check your bank account from your computer, a client program in your computer forwards your request to a server program at the bank. That program may in turn forward the request to its own client program that sends a request to a database server at another bank computer to retrieve your account balance. The balance is returned back to the bank data client, which in turn serves it back to the client in your personal computer, which displays the information for you.<br />The client/server model has become one of the central ideas of network computing. Most business applications being written today use the client/server model. So does the Internet's main program, TCP/IP. In marketing, the term has been used to distinguish distributed computing by smaller dispersed computers from the "monolithic" centralized computing of mainframe computers. But this distinction has largely disappeared as mainframes and their applications have also turned to the client/server model and become part of network computing.<br />In the usual client/server model, one server, sometimes called a daemon, is activated and awaits client requests. Typically, multiple client programs share the services of a common server program. Both client programs and server programs are often part of a larger program or application. Relative to the Internet, your Web browser is a client program that requests services (the sending of Web pages or files) from a Web server (which technically is called a Hypertext Transport Protocol or HTTP server) in another computer somewhere on the Internet. Similarly, your computer with TCP/IP installed allows you to make client requests for files from File Transfer Protocol (FTP) servers in other computers on the Internet. Other program relationship models included master/slave, with one program being in charge of all other programs, and peer-to-peer, with either of two programs able to initiate a transaction.</span> </div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/37066558-116256087411307202?l=compu-sc.blogspot.com' alt='' /></div>Amit Ranjanhttp://www.blogger.com/profile/08501750120817164659noreply@blogger.com0