Content deleted Content added
Christoofar (talk | contribs) No edit summary |
Christoofar (talk | contribs) No edit summary |
||
Line 1:
In [[computer programming]], an '''object cesspool''' is an [[antipattern]] that occurs whenever an [[object pool]] contains 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.
Oftentimes, the afflicted software will yield unpredictable and sporadic results when performing operations that seem routine. This problem arises when used objects returned from the pool to a client which are in a state that is incompatible with the expected operation of the client. The problem is also more apparent in object pools which contain class instances that are very complex as opposed to simpler classes with few properties and/or methods.
| |||