The idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

For more visit :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by Ni .. , an ibibo Master, at 9:05 PM on July 22, 2008

The idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

For more visit :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by R.P. Singh , an ibibo Master, at 6:29 PM on July 22, 2008

The idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

For more visit :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by ashish Yadav , an ibibo Wizard, at 3:37 PM on July 21, 2008

The idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

Source Site could give you more information :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by Rocky , an ibibo Master, at 8:23 PM on July 19, 2008

idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

Source Site :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by .... ..... , an ibibo Master, at 11:19 AM on July 16, 2008

The idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

Source Site could give you more information :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by Sharad Singh , an ibibo Master, at 6:21 PM on July 15, 2008

idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

Source Site :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by Raksha , an ibibo Master, at 9:18 AM on July 11, 2008

well, The idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

Source Site could give you more information :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by Romi , an ibibo Master, at 1:39 PM on July 06, 2008

idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

Source Site :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by Gyan Singh , an ibibo Master, at 9:17 AM on June 30, 2008

idea of object pooling is similar to the operation of your local library. When you want to read a book, you know that it's cheaper to borrow a copy from the library rather than purchase your own copy. Likewise, it is cheaper (in relation to memory and speed) for a process to borrow an object rather than create its own copy. In other words, the books in the library represent objects and the library patrons represent the processes. When a process needs an object, it checks out a copy from an object pool rather than instantiate a new one. The process then returns the object to the pool when it is no longer needed.

Source Site :

http://www.javaworld.com/ jw-06 -1998/jw-06-object-pool.html

Answered by Madhurima , an ibibo Master, at 6:13 PM on June 26, 2008