I think there is something to be said for keeping TaskManager, with an
interface that hides how the thread pooling is implemented, and having
all uses of this sort of threading use it. That way, we can change the
implementation in one place. java.util, for example, was improved
between 1.5 and 1.6, and we may want to use 1.6 features in a future
implementation.
Patricia
On 7/25/2010 1:32 AM, Peter Firmstone wrote:
Something I need to consider is that I intend to support Java CDC 1.11
Personal Basis Profile, this will be a subset of the Jini API using
JERI, in place of java RMI, only to allow simple service participation,
there's no intent to have all the existing Service implementations run
on it, just the basics.
CDC enables supporting, blue ray players, Amazon Kindle and TV set top
boxes, no phones unfortunately, that seems to have died. The existing
ServiceUI enable's support of various User interfaces for different
platforms.
For that reason, we should probably prefer com.sun.jini.thread.Executor
over java.util.concurrent.Executor in any API.
One implementation can map to the other.
