Accesing UI thread with Async task?

I usually use inner classes for this and see no reason why this should be a bad solution, assuming the class implementation is specific to the class into which it's nested.

Up vote 0 down vote favorite share g+ share fb share tw.

Passing Context into AsyncTask feels 'dirty' but I don't know whether it's ok 'polluting' the UI class. Android android-asynctask link|improve this question asked Aug 11 '11 at 0:31Jon Romero7591722 74% accept rate.

– NoobyBooby Aug 11 '11 at 1:18 I like having my tasks in a separate file but yes, it's plausible :D – Jon Romero Aug 16 '11 at 19:15.

If you are not going to extend your class in future with another class, then extend it. But I'd rather choose passing the context in the constructor.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.