BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Feedo Feed//NONSGML v1.0//EN
METHOD:PUBLISH
X-WR-CALNAME:Updated: Concurrency in Android by Blake Meike at 541 8th St, San Francisco, CA - Java on Plancast
X-WR-CALDESC:Update: The Mobile Web / Chrome talk by Google is postponed until we get the complete abstract from Google and secure a new date. We'll keep you...
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:UTC
X-LIC-LOCATION:UTC
BEGIN:STANDARD
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
DTSTART:19700101T020000
RRULE:FREQ=YEARLY;BYMONTH=1;BYDAY=1TH
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=UTC:20120731T180000Z
DTEND;TZID=UTC:20120731T180000Z
UID:a529822@plancast.com
SUMMARY:Updated: Concurrency in Android by Blake Meike
DESCRIPTION:Update: The Mobile Web / Chrome talk by Google is postponed until
 we get the complete abstract from Google and secure a new date.
 We'll keep you posted. Sorry for the inconvenience.\n
 \n
 Instead\, we'll have Blake Meike\, from Marakana\, and a
 co-author of Programming Android\, give a talk focused on the
 concurrency best-practices in Android.\n
 \n
 Moblie appliances change the nature of the concurrent demands put
 on applications and the operating systems that support them.
 Until very recently\, concurrency was an optimization trick that
 allowed an expensive machine to service a queue of tasks
 effectively. Instead of waiting for something real-world and
 slow\, it could do work on other queued tasks.\n
 \n
 With mobile appliances “concurrency” means something
 more like what used to be called “real time computing”.
 A mobile device user may be\, simultaneously\, using a web
 browser\, listening to music\, taking direction from a navigation
 service\, and receiving text and phone calls. Furthermore
 multi-core processors are becoming common on mobile platforms:
 true concurrency will replace synchronous processor sharing.\n
 \n
 The Android OS includes tools at three levels of granularity (in
 addition to those standard in java.util.concurrent)\, to address
 the need for concurrent execution: the managed application
 lifecycle\, the Looper/Handler types\, and the AsyncTask
 template. While these tools are partially successful each
 introduces its own new problems. In particular\, the interactions
 between the managed application lifecycle and the AsyncTask can
 be especially problematic.\n
 \n
 The venue\, food\, drinks\, and giveaways will be provided by our
 sponsors.\n
 \n
 About Blake Meike:\n
 \n
 Blake is an engineer with more than 30 years of experience\, much
 of it with Java.  He has built systems as large as Amazon's
 massively scalable AutoScaling service and as small as a
 pre-Android OSS/Linux based Java-like platform for cell-phones.
 He is co-author of the O'Reilly book\, "Programming Android". He
 teaches Android at Marakana.\n
 When: Tuesday\, July 31\, 2012 at 6:00 PM\n
 Where: StackMob HQ \n
 Attendees: 10 http://plancast.com/p/bcta
URL:http://plancast.com/p/bcta
CATEGORIES:Java,Open Source,Software Developers,Google,Mobile Technology,Android Developers,Android,Mobile
LOCATION:StackMob HQ 
DTSTAMP:20120510T015239Z
END:VEVENT
END:VCALENDAR