Object cesspool: Difference between revisions

Revision as of 20:55, 5 October 2005

Revision as of 01:45, 6 October 2005

Line 1:

<!-- Please do not remove or change this AfD message until the issue is settled -->

<div class="boilerplate metadata" id="afd" style="margin: 0 5%; padding: 0 7px 7px 7px; background: #EDF1F1; border: 1px solid #999999; text-align: left; font-size:95%;">

'''This article is being considered for deletion in accordance with Wikipedia's [[Wikipedia:Deletion policy|deletion policy]][[Template:Afd|.]]'''<br />

Please share your thoughts on the matter at '''[[Wikipedia:Articles for deletion/{{PAGENAME}}|this article's entry]]''' on the Articles for Deletion page.<br />

You are welcome to edit this article, but please do not blank this article or remove this notice while the discussion is in progress. For more information, particularly on merging or moving the article during the discussion, read the [[Wikipedia:Guide to deletion|Guide to Deletion]].</div>

[[Category:Pages for deletion]]

<!-- End of AfD message, feel free to edit beyond this point -->

In [[computer programming]], an '''object cesspool''' is an [[antipattern]] that occurs whenever an [[object pool]] contains stateful class instances that were used by a client, but the used objects are not returned to a useable state when released back to the pool and/or the evidence of the use of the object is not reset prior to returning the object to new clients.