Re: [equinox-dev] a future with futures

[Thomas Watson <tjwatson@xxxxxxxxxx>]

How big is the code? I got the impression that is is not going to be that big (perhaps 20k or less)?

I agree with Pascal that it would be nice to separate this into another bundle, but I would like to avoid splitting it into a whole bunch of very small bundles. Would it be possible to move JobsExecutor and RealmJobsExecutor into the jobs bundle and have jobs depend on the new equinox futures package? The other option is to have optional dependencies on jobs, but I think it is cleaner to put them into the jobs bundle. If we moved the jobs related classes to jobs the package could be something like org.eclipse.core.jobs.future. I am fine with org.eclipse.equinox.future as the bundle/package name.

Thoughts?

Tom



Scott Lewis ---01/14/2009 09:25:49 PM---Hi Pascal,

From:	Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>
To:	Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Date:	01/14/2009 09:25 PM
Subject:	Re: [equinox-dev] a future with futures

---

Hi Pascal,

I'm willing to do this, if this is the consensus...but it would probably 
then need to be two bundles...since the two jobs-dependent classes 
(JobsExecutor and RealmJobsExecutor) would best be isolated from the 
rest (which only have deps on org.eclipse.core.runtime).

What package naming do people suggest? 

Thanks,

Scott

Pascal Rapicault wrote:
>
> The code seems to be relatively well isolated, why not create a new 
> bundle for it?
>
> Inactive hide details for Scott Lewis ---01/14/2009 07:17:19 PM---On 
> this E4 enhancement request: https://bugs.eclipse.org/bugScott Lewis 
> ---01/14/2009 07:17:19 PM---On this E4 enhancement request: 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=253777
>
>
> From: 		 
> Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>
>
> To: 		 
> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>
> Date: 		 
> 01/14/2009 07:17 PM
>
> Subject: 		 
> [equinox-dev] a future with futures
>
> ------------------------------------------------------------------------
>
>
>
> On this E4 enhancement request:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=253777
>
> there has been a long and fruitful discussion about supporting
> asynchronous programming (for E4 as well as other projects including
> ECF, p2, DSDP) by adding the concept of a 'future' to Equinox.  Various
> designs have been proposed, and I think that there has been a good
> amount of convergence recently...i.e. see comment 121:  
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=253777#c121 for a recent
> summary.
>
> I would like to request that this contribution be considered for
> addition to Equinox for the Galileo release cycle.  If there is
> more/other that I can do as a contributor please let me know.
>
> Scott
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>   

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev