commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15339] - StackObjectPool needs to ensure available objects in pool are unique
Date Fri, 18 Apr 2003 21:50:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15339>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15339

StackObjectPool needs to ensure available objects in pool are unique

rwaldhoff@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER



------- Additional Comments From rwaldhoff@apache.org  2003-04-18 21:50 -------
Let's pick this up after a 2.0 release.   The "proposal" I never quite got
around to posting is to refactor ObjectPool and ObjectFactory a bit to allow for
composing behaviors in functor style.  This will allow one to add an "make sure
each object is only returned once" aspect to an arbitrary pool (not just
StackObjectPool), but won't force it on others who might not want the overhead.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message