<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 2011-08-18 19:52, Chris Irwin wrote:
<blockquote cite="mid:20110818235232.GC4107@thinkpad" type="cite">
<pre wrap="">My experience with WebOS is that non-focused apps do continue to work.
This can be illustrated by opening a browser to a web page, then switch
to another app. When you switch back, the browser will have fetched the
page.
</pre>
</blockquote>
<tt>AFAIK (as an Android newbie *): This is the same on Android.<br>
<br>
Thanks to Norm Young's presentation, when an Android app is switched
out, the Activity component is suspended by the other components (if
any) in the app remain active.<br>
<br>
<Qualifier> However, If one of these other components is waiting
for a response from the Activity component, e.g. user interaction, then
the waiting component will be blocked - in the Android
framework.</Qualifier><br>
<br>
Referring to Norm's presentation the five architectural components of
an Android app are:<br>
</tt>
<ul>
<li><tt><em>Activity</em> - User interaction</tt></li>
<li><tt><em>Service</em> - Long-running computation</tt></li>
<li><tt><em>Broadcast Receiver</em> - System event reception</tt></li>
<li><tt><em>Content Provider</em> - Data access and storage</tt></li>
<li><tt><em>Intent</em> - Inter-component communication</tt></li>
</ul>
<tt>* 2 introductory meetings on developing for Android hardly qualify
me as an advisor in this space. <br>
But that has never stopped me before ;-)<br>
<br>
Regards<br>
jsquared<br>
</tt><br>
</body>
</html>