[concurrency-interest] ScheduledThreadPoolExecutor woes

Hanson Char hanson.char at gmail.com
Mon Feb 12 17:15:09 EST 2007


Also, it would be really nice if the javadoc of the retry related classes
can be published somewhere at jcip similar to the one for the annotations:

  http://jcip.net/annotations/doc/

Hanson

On 2/7/07, Hanson Char <hanson.char at gmail.com> wrote:
>
> Excellent!  The existing RetryPolicies compiles only under Java 5 (not
> Java 6).  I've fixed up a version that preserves all the generics but
> compiles only under Java 6.  Can send you a copy if interested.
>
> Hanson
>
> On 2/7/07, Tim Peierls <tim at peierls.net> wrote:
> >
> > Thanks! Could you post AbstractRetryPolicy? I can't find it.
> >
> > --tim
> >
> > On 2/7/07, Joshua Bloch <josh at bloch.us > wrote:
> > >
> > > Sure; I dont' think public domain will cause any problems.  Google and
> > > I hereby release it into the public domain. (It may end up in the JDK some
> > > day, but it may not.)
> > >
> > >                  Josh
> > >
> > > On 2/7/07, Tim Peierls <tim at peierls.net> wrote:
> > > >
> > > > I don't know. Best thing would be for Josh to decide how he wants it
> > > > distributed.
> > > >
> > > > --tim
> > > >
> > > > On 2/7/07, Hanson Char < hanson.char at gmail.com> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Can I presume the jcip/retry/*.java source code is in the public
> > > > > domain ?  If not, please kindly advise the licensing used.
> > > > >
> > > > > Thanks,
> > > > > Hanson
> > > > >
> > > > > Josh told me he'd be willing to distribute this more widely if
> > > > > > there was sufficient interest.
> > > > > >
> > > > > > I've placed an incomplete draft of this code in a public area of
> > > > > > the Java Concurrency in Practice source repository:
> > > > > >
> > > > > > https://dev.priorartisans.com/repos/jcip/trunk/src/main/jcip/retry/
> > > > > >
> > > > > >
> > > > > > It's incomplete because it doesn't define AbstractRetryPolicy.
> > > > > >
> > > > > > What Bela describes is slightly different: each task can be
> > > > > > submitted with its own "RetryPolicy". That could be achieved within Josh's
> > > > > > framework, for example, by extending ScheduledThreadPoolExecutor and
> > > > > > overriding decorateTask to do the requisite wrapping for tasks that
> > > > > > implement RetryPolicy.
> > > > > >
> > > > > > --tim
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20070212/fa7be378/attachment.html 


More information about the Concurrency-interest mailing list