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 13856] - Sharing eviction threads
Date Wed, 30 Oct 2002 17:55:47 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=13856>.
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=13856

Sharing eviction threads





------- Additional Comments From roytmana@peacetech.com  2002-10-30 17:55 -------
Yes exposing a doEviction() will enable me to initiate eviction as I need it 
and will be sufficient for me. 
Hovewer I think Commons-Pool should provide some out of the box "default" 
eviction schediler like background daemon thread you use now. 
I think using java.util.Timer or similar techniques is preferable to using 
background daemon thread per pool primarily because it is external to pool and 
can be shared by multiple pools

In case of java.util.Timer we would need:
- Extend Evictor class from java.util.TimerTask
- Add pool level method getEvictorTask() to return pool's evictor so it can be 
subscribed to listen for timer event. 

Evictor can implement several "Task" interfaces to support different schedulers 
i.e. ejb timer service etc. But I am not sure it should because we are 
talking "default most commonly used" implementation and for other cases 
exposing doEviction() will be sufficient.


Thank you very much for following up on this

I am not subscribed to commons mailing list but if you think it worth futher 
discussion please let me know and I will subscribe to the list

Alex Roytman

roytmana@peacetech.com

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


Mime
View raw message