Basic overview of how Ion works

[hoda0013]

Can someone give me a basic overview of how this codebase does what it does (Ion / Android Async).

Specifically I'd like to know:

1) Is the networking done in the same process as the application you're integrating it into? 2) Is the networking done in an Android component like a Service? 3) What happens if the application is killed from the 'recents' task list during a network call? Does the networking stop or is it allowed to finish what it was doing? 4) Can you take me through the series of steps that occur once I build my Ion command and initiate a networking operation? (i.e. first an executor is created, then...)

I am only concerned with the basic case of doing POST or a GET with json, not using bitmaps, image transformations, etc...

[jirevwe]

Hi,

I'm not an expert nor did I write any code for this. I use this library for some things, if it doesn't work the way I want it to, i write it from scratch.

1) Is the networking done in the same process as the application you're integrating it into? Ans: Yes it is. Once the Context (Activity or fragment is closed), the network connection terminates.

2) Is the networking done in an Android component like a Service? Ans: No its not, It's done in a background thread.

3) What happens if the application is killed from the 'recents' task list during a network call? Does the networking stop or is it allowed to finish what it was doing? Ans: From my experience using it, the whole progress stops, once the app is cleared from the task list.

4) Can you take me through the series of steps that occur once I build my Ion command and initiate a networking operation? (i.e. first an executor is created, then...) Ans: I dunno the inner workings, but to have an idea, turn on the Ion logger Ion.getDefault(this).configure().setLogging("ion-sample", Log.DEBUG);