Talk:Object pool

From Wikipedia, the free encyclopedia

My English writing skills aren't up to much, so I can't really clean up this article, but I'm happy to monitor the technical content, and ensure that a rewrite by someone with English skills (but no tech knowledge) doesn't get the tech wrong.

Rewrite done - could do with checking over by a Wikipedia regular 80.175.251.18 11:44, 16 March 2006 (UTC)

[edit] Moved from Talk:Object cesspool

This article was nominated for deletion on 6 October 2005. The result of the discussion was merge with Object pool. An archived record of this discussion can be found here.

This article has little value. It might as well be called "I had some bugs in my code that were interesting to me, and I came up with a cute name for it."

Above was by 200.122.153.250

[1] has a comment by user "christoofar" "This is offtopic, but Oliver Klozoff and I have finally finished battling a problem with a C++ component written at my company that warranted a new design antipattern article (I added it to wikipedia) http://en.wikipedia.org/wiki/Object_cesspool"

I'm going to nominate this on AFD because it seems to be a neologism; and should be on the Portland repository [2] first if it was notable. (In my blatently POV opinion, I think it's fairly apparent to anyone trying to write an object pool.) -Tenbaset 00:34, 6 October 2005 (UTC)

I have just extended object pool to include a brief (and poorly written) explanation of object cesspools. -195.173.15.12 11:05, 6 October 2005 (UTC)

Since the term is in common use, this page is valuable.

Please provide references if this is the case --163.118.128.194 15:21, 18 October 2005 (UTC)

[edit] Definition of an Object Pool

I've added some external references and links. There seems to be some confusion over what exactly an object pool is. For example, this Inform IT article classifies it as a memory pattern rather than as a creational pattern, and describes it slightly differently as "Pool Allocation Pattern works well by creating pools of objects, created at startup, available to clients upon request", whereas many other sources describe this pattern more as a recycling method that can still dynamically allocate objects on demand if one isn't already available in the pool. e.g., from the EuroPlos conference paper: "To increase efficiency, the resource pool eagerly acquires a static number of resources after creation. If the demand exceeds the available resources in the pool, it lazily acquires more resources." Saigyo 11:32, 9 June 2007 (UTC)