1. Android
HTTP Service
By:
Eduardo Silva edsiper@monkey-project.com
Jonathan Gonzalez zeus@monkey-project.com

2. < Goal >
“Empower Android devices with an
HTTP Service layer where applications
and framework components can expose
their own HTTP Service through an
unique low level component.”

3. < Android Architecture >

4. Our proposal...

5. < Our proposal >
Add an HTTP
service layer
into the app
framework.

6. < Terms used >
● Instance = web server process
● Requester = any SW component that request to
own a service
● Service = Unique URI address used to identify
communication with a requesters :
e.g: http://192.168.1.1/STATUS

7. < HTTP Service / Roles >
● Handle web server instances
● Register services for requesters
● Proxy web server communication

8. Communication Diagram

10. How ?

11. ● HTTP Service
application written in Java compliant with
Dalvik virtual machine, it exports
com.android.http_service.*
● Instance
Monkey HTTP Daemon (web server)
● How Instances and HTTP Service talk ?
Through Monkey plugin + unix sockets

12. Why Monkey ?

13. …because
Monkey Loves Android
Monkey Features
● It's a web server designed for embedded devices
● It's asynchronous, events oriented
● It has a flexible Plugin interface (API)
● It's binary size is only 55 KB
● It's very very fast

14. We expect to implement this
HTTP layer through GsoC 2011,
this is a really good improvement!
Monkey Team