I apologize if I appear to have been brusque, I'm just busy. I've heard here some say that we should avoid 'framework-like' things in [lang], and the interface feels a touch like that. Also, we want to avoid, IMHO, the possibility of feature creep that ends up being JSR-166-like.
Gary > -----Original Message----- > From: James Carman [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 17, 2005 10:28 AM > To: 'Jakarta Commons Developers List' > Subject: RE: [lang] Concurrency Classes... > > It was just a thought. I am using similar code in commons-collections to > implement BlockingBuffer, TimeoutBuffer, and BoundedBuffer. So, I thought > it might be common enough for commons-lang, since it doesn't depend on > anything but core Java. I wasn't saying that we should implement all the > Oswego/JSR-166 stuff. I just needed these two specific methods. > > -----Original Message----- > From: Gary Gregory [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 17, 2005 1:17 PM > To: Jakarta Commons Developers List > Subject: RE: [lang] Concurrency Classes... > > I am against it. That's what JSR-166 is for, which is built-in to Java 5 > and available as add-ons for Java 1.3.1 and and 1.4. > > >From the spec author, this version, runs on both Java 1.3.1 and 1.4.2: > > http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/int > ro.html > > The backport-util-concurrent, version 2.0_01, which runs on top of Java > 1.4, is available here: > > http://www.mathcs.emory.edu/dcl/util/backport-util-concurrent/ > > Gary > > > -----Original Message----- > > From: James Carman [mailto:[EMAIL PROTECTED] > > Sent: Thursday, November 17, 2005 8:17 AM > > To: 'Jakarta Commons Developers List' > > Subject: [lang] Concurrency Classes... > > > > All, > > > > What do you think about adding in some classes which can help deal > with > > doing blocking waits on lock objects? Something like: > > > > public class BlockingUtils { > > public void waitUntil( Object lock, long timeout, Condition > condition ) > > throws InterruptedException, TimeoutException; > > > > public void waitUntil( Object lock, Condition condition ) throws > > InterruptedException; > > } > > > > // We could use something from functor here, but to avoid the > > dependency... > > public interface Condition { > > public boolean evaluate(); > > } > > > > public class TimeoutException extends Exception { > > } > > > > James > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
