[
https://issues.apache.org/jira/browse/DROIDS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017877#comment-13017877
]
Eugen Paraschiv commented on DROIDS-56:
---------------------------------------
I see, and will using a pool size of one mean that the execution will be
contained in the current running thread, or will it create a new thread? If
it's the latter, then the problem remains - the change introduces
asynchronicity in the execution, which deeply affects client code and
introduces all kinds of race conditions in formerly serial code that used
SequentialTaskMaster.
> Change the TaskQueue interface to java.util.Queue
> -------------------------------------------------
>
> Key: DROIDS-56
> URL: https://issues.apache.org/jira/browse/DROIDS-56
> Project: Droids
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.0.1
> Reporter: Mingfai Ma
> Assignee: Bertil Chapuis
> Fix For: 0.0.1, 0.0.2
>
> Attachments: Queue.diff, droids-56-v2.diff, droids-56.diff,
> taskQueue-to-queue.diff
>
>
> 1. any code that depends on the queue should depend on java.util.Queue<T>
> rather than TaskQueue.
> 2. either remove the TaskQueue or make it extends java.util.Queue
> - it means SimpleTaskQueue should extends a Queue implementation (or
> implement all method of a Queue)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
