Why did google choose C/S architecture in android camera?

Question

As we know , android camera is the C/S architecture, including the client and the service. They communicate each other by the Binder. They are running in different process.

So I have a question : why android camera have a client and service ? What's the advantage?

Probably Client=Hardware camera & Server=Service to access Client... — Raynold, Mar 20 '13 at 11:04
@Raynold In fact, App.Camera-->Frameworks.Camera -->Jni--> Client --> Service — Jerikc, Mar 20 '13 at 11:08

Artem Zinnatullin · Accepted Answer · 2013-03-25T09:14:15.477

May be they choosed C/S architecture, because it is better for sending notifications to listeners, for example Dropbox and Google+ app are listening for photo events for uploading new photos to cloud. Also, you can subscribe your app for same events too (with ACTION_IMAGE_CAPTURE). So, they not watching for changes in DCIM folders, they subscribe to system events.

With just client arhitecture, photo apps will have implement sending of all camera events to provide compatibility to other apps.

But it is just my opinion :)

Why did google choose C/S architecture in android camera?

1 Answers1