As long as you have the default pool-size set to 1, there should be no
issues what-so-ever.
On Jun 27, 8:00 am, joshv wrote:
> Interesting issue. I can see the need to make this configurable
> though. In some cases it would be nice to make sure that these
> background tasks do not run concurre
Interesting issue. I can see the need to make this configurable
though. In some cases it would be nice to make sure that these
background tasks do not run concurrently as concurrency issues can
result.
For example, I might have a URL fetch tied to a user interface
button. When the URL returns,
Thanks Romain for quick response.
Jayesh
On Fri, Jun 26, 2009 at 10:54 PM, Romain Guy wrote:
>
> Hi,
>
> It's a bug and your workaround is correct. I'll fix this right away.
>
> On Fri, Jun 26, 2009 at 9:27 AM, Jayesh Salvi
> wrote:
> > Hi,
> >
> > I am replacing the multithreaded code in my ap
Hi,
It's a bug and your workaround is correct. I'll fix this right away.
On Fri, Jun 26, 2009 at 9:27 AM, Jayesh Salvi wrote:
> Hi,
>
> I am replacing the multithreaded code in my app with the AsyncTask from 1.5.
> I found that two AsyncTasks do not work concurrently. I investigated a bit
> and
4 matches
Mail list logo
