Hi,
You should always put long operations in a separate threads. Failing
to do so will block the UI thread and thus prevent redraws and all
user interactions.
On Mon, Jun 9, 2008 at 10:52 AM, Danny <[EMAIL PROTECTED]> wrote:
>
> I know in J2ME, it was good practice to put any blocking operations in
> Threads, does this apply to Android as well? Examples I've seen so
> far don't seem too, maybe they were just being lazy.
>
> Here is example of what I'm talking about.
>
> Thread t = new Thread() {
> public void run() {
> connect();
> }
> };
> t.start();
>
> private void connect() {
> ...
> URLConnection conn = aURL.openConnection();
> conn.connect();
> InputStream is = conn.getInputStream();
> ...
> }
>
> Or can I safely just call 'connect()' on its own and just handle
> interruptions and what not by utilizing the onFreeze() and related
> methods?
>
> >
>
--
Romain Guy
www.curious-creature.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
