Asynctask with one or more methods

Question

I would like to know the advantages and disadvantages of using an extended class of AsyncTask, which contains only one or more methods.

Example:

• I create a AsyncTask for each background processing that I will utilise.

or

• I create a AsyncTask for all processing, and within it I create several methods, and I call them with a parameter when instantiating the class ?

It is something to be considered, or only in terms of organization, need, preference, or even good practices ?

Answer 1

Not only in this case but whatever the situation may/should consider other approaches.

However it should take into account not the organisation, necessity, preference, or even good practice but rather what is most appropriate for the situation in question.

You should start by considering using an Asynctask for each processing.
If, during development, you find that there are processes with similar characteristics you may consider writing a single class to process them.

Not in the way you describe your second example, which, if I have understood correctly, will require the implementation of some logic to be able to handle the different processing. This will not only complicate the class but complicate its use.

That’s why I mentioned "processing with similar characteristics". For example, if you have a set of processes that do not return anything and require a Progressbar to be displayed, you can write an extended Asynctask class where you implement all methods except the doInBackground().

When you have such a processing all you need to do is implement this method:

new GenericAsyncTask() {
    @Override
    protected Void doInBackground(Void... voids) {

        //inserir aqui o processamento a executar
        return null;
    }
}.execute();

This is just one example, others will depend on the type of processing.